On Sat, 2009-06-27 at 22:18 +1000, Saul Lethbridge wrote: > So can I assume that this means I can no longer lose an event?
let me clarify: you could have "lost" the last motion event *in a series of events being throttled*, with the previous code. now the code reads ahead and will throttle motion events in the middle so you'll always get at least the last motion event. > How can I see if motion events are being throttled or lost? you can only have the motion events Clutter gives you, and the motion events are throttled if they happen between redraws. so the distinction between "lost" and "throttled" is fictitious. neither you should really care: at most, you'll get a 5 milliseconds interval between a motion event an the next, unless you're hogging the CPU during your motion event handlers -- in which case "you're doing it wrong", as the kids today say. ciao, Emmanuele. > On Sat, Jun 13, 2009 at 6:31 PM, Emmanuele Bassi > <[email protected]> wrote: > On Sat, 2009-06-13 at 08:30 +1000, Saul Lethbridge wrote: > > It seems the function clutter_set_motion_events_ frequency > has been > > removed recently. Has it been replaced by another function? > > > all the throttling for the motion events passes through the > newly added > master clock, so if you don't have sync-to-vblank support it > will use > the default frame rate: > > clutter_set_default_frame_rate() > > this also prevent you from losing the last motion event in > case it was > throttled. > > ciao, > Emmanuele. > > -- > Emmanuele Bassi, Senior Engineer | > [email protected] > Intel Open Source Technology Center | http://oss.intel.com > > -- > To unsubscribe send a mail to [email protected] > > -- Emmanuele Bassi, Senior Engineer | [email protected] Intel Open Source Technology Center | http://oss.intel.com -- To unsubscribe send a mail to [email protected]
