summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJulien Moutte <julien@moutte.net>2004-01-28 00:29:42 +0000
committerJulien Moutte <julien@moutte.net>2004-01-28 00:29:42 +0000
commitc924e8a070cf8fadb4882738830936ea845a8033 (patch)
treefec8b48034bd2d972dc88c0487bd23f3414d8103
parent0e61e9951babe9feb75a3b032724a180f98876e0 (diff)
downloadgst-plugins-bad-c924e8a070cf8fadb4882738830936ea845a8033.tar.gz
gst-plugins-bad-c924e8a070cf8fadb4882738830936ea845a8033.tar.bz2
gst-plugins-bad-c924e8a070cf8fadb4882738830936ea845a8033.zip
sys/: Our
Original commit message from CVS: 2004-01-28 Julien MOUTTE <julien@moutte.net> * sys/ximage/ximagesink.c: (gst_ximagesink_handle_xerror), (gst_ximagesink_check_xshm_calls), (gst_ximagesink_ximage_destroy), (gst_ximagesink_xcontext_get), (gst_ximagesink_class_init): * sys/xvimage/xvimagesink.c: (gst_xvimagesink_handle_xerror), (gst_xvimagesink_check_xshm_calls), (gst_xvimagesink_xvimage_destroy), (gst_xvimagesink_xcontext_get): Our X plugins are now able to detect that XShm calls will fail even if the server claims that it has XShm support (remote displays most of the time). We then log the error as a GST_DEBUG and set use_shm to FALSE so that we use non XShm functions. This feature is almost useless for xvimagesink as Xv is not supported on remote displays anyway, but it might happen than even on the local display XShm calls fail.
-rw-r--r--ChangeLog15
1 files changed, 15 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index 60936543..795d0092 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,18 @@
+2004-01-28 Julien MOUTTE <julien@moutte.net>
+
+ * sys/ximage/ximagesink.c: (gst_ximagesink_handle_xerror),
+ (gst_ximagesink_check_xshm_calls), (gst_ximagesink_ximage_destroy),
+ (gst_ximagesink_xcontext_get), (gst_ximagesink_class_init):
+ * sys/xvimage/xvimagesink.c: (gst_xvimagesink_handle_xerror),
+ (gst_xvimagesink_check_xshm_calls),
+ (gst_xvimagesink_xvimage_destroy), (gst_xvimagesink_xcontext_get): Our
+ X plugins are now able to detect that XShm calls will fail even if the
+ server claims that it has XShm support (remote displays most of the
+ time). We then log the error as a GST_DEBUG and set use_shm to FALSE
+ so that we use non XShm functions. This feature is almost useless for
+ xvimagesink as Xv is not supported on remote displays anyway, but
+ it might happen than even on the local display XShm calls fail.
+
2004-01-27 David Schleef <ds@schleef.org>
* ext/esd/esdsink.c: (gst_esdsink_class_init), (gst_esdsink_init),