From cfd945ea263496bebb5beaf5b9a6b980def890ac Mon Sep 17 00:00:00 2001 From: David Schleef Date: Tue, 20 Jan 2004 09:25:51 +0000 Subject: [PATCH] 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 --- ChangeLog | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/ChangeLog b/ChangeLog index f7b59534fe..915d96e707 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,13 @@ +2004-01-20 David Schleef + + * 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 * configure.ac: