Re: [gtk-vnc-devel] [PATCH 4/7] Compress motion events to the VNC connection can keep up 2008-11-20 Federico Mena Quintero <federico novell com>

["Daniel P. Berrange" <berrange redhat com>]

On Thu, Nov 20, 2008 at 02:54:38PM -0600, Federico Mena Quintero wrote:
> 	Do compression of motion events, like TightVNC does, so that the
> 	VNC connection can keep up with the events we send.
> 
> 	* src/vncdisplay.c (realize): Add a GtkWidget::realize handler.
> 	We install an event filter for our window, so that the filter can
> 	eat pending motion events.
> 	(eat_pending_motion_events_filter_func): New window filter
> 	function.  We eat all pending motion events in the X event queue.

So, if I'm understanding this correctly, if there's 20 pending motion
events in a row, it'll skip over the first 19, and just process the
last. This seems like a reasonable optimization - shame there's no
way to do this in GTK though, rather than raw X calls .

We'd need to #ifndef it for Win32 if GTK can't do it

Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|