summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDavid Schleef <ds@schleef.org>2004-01-20 09:25:51 +0000
committerDavid Schleef <ds@schleef.org>2004-01-20 09:25:51 +0000
commitcfd945ea263496bebb5beaf5b9a6b980def890ac (patch)
tree0138549726e5517638ddafca7a449f085482914f
parent6eabfea8cb3c3393fec1d0415759947f1bc88548 (diff)
sys/ximage/ximagesink.c: Change to using a framerate of [1,100] instead of [0,MAX], since 0 isn't handled correctly, ...
Original commit message from CVS: * sys/ximage/ximagesink.c: (gst_ximagesink_handle_xevents), (gst_ximagesink_xcontext_get), (gst_ximagesink_getcaps), (gst_ximagesink_set_xwindow_id): Change to using a framerate of [1,100] instead of [0,MAX], since 0 isn't handled correctly, and neither is 100+, most likely. * sys/xvimage/xvimagesink.c: (gst_xvimagesink_get_xv_support), (gst_xvimagesink_getcaps): same
-rw-r--r--ChangeLog10
1 files changed, 10 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index f7b59534..915d96e7 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,13 @@
+2004-01-20 David Schleef <ds@schleef.org>
+
+ * sys/ximage/ximagesink.c: (gst_ximagesink_handle_xevents),
+ (gst_ximagesink_xcontext_get), (gst_ximagesink_getcaps),
+ (gst_ximagesink_set_xwindow_id): Change to using a framerate
+ of [1,100] instead of [0,MAX], since 0 isn't handled correctly,
+ and neither is 100+, most likely.
+ * sys/xvimage/xvimagesink.c: (gst_xvimagesink_get_xv_support),
+ (gst_xvimagesink_getcaps): same
+
2004-01-19 Benjamin Otte <in7y118@public.uni-hamburg.de>
* configure.ac: