After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 320113 - [API] duration message changes
[API] duration message changes
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.9.x
Other Linux
: Normal normal
: 0.9.6
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks: 319388
 
 
Reported: 2005-10-28 18:07 UTC by Tim-Philipp Müller
Modified: 2005-11-21 10:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tim-Philipp Müller 2005-10-28 18:07:44 UTC
(1)
Rename GST_MESSAGE_DURATION => GST_MESSAGE_DURATION_CHANGED


(2)
GstMessage * gst_message_new_duration (GstObject *src, 
                                       GstFormat format, 
                                       gint64 duration);

  becomes

GstMessage * gst_message_new_duration_changed (GstObject *src);


(3)
void  gst_message_parse_duration (GstMessage *message, GstFormat *format, gint64
*duration);

isn't required any longer.



<wtay> __tim, duration queries can be quite expensive
<wtay> __tim, I don't want to app to poll for it but get a notify when it
changed, then let the app choose how many times it performs the expensive work
<__tim> so if it's expensive, the element posts a DURATION message with duration
= -1 ?
<wtay> __tim, actually the value in the message is not used
<wtay> __tim, it's in the API but it's not usable in the end
<wtay> __tim, the purpose of the message is to notify that the duration changed
and the exact new value can be retrieved with a query

Cheers
 -Tim
Comment 1 Wim Taymans 2005-11-20 15:18:49 UTC
the duration message is used internally to replay to duration queries much
faster, the previous duration is stored in the message so we cannot remove it.
We could add a DURATION_CHANGED message in addition to the existing DURATION
message but that seems silly.
Comment 2 Tim-Philipp Müller 2005-11-21 10:42:52 UTC
Alright, leaving the API as is then and updated the documentation to reflect
intended usage.
Comment 3 Wim Taymans 2005-11-21 10:46:16 UTC
yep, last CVS commit is the best.