GNOME Bugzilla – Bug 667989
GSocket GSocketSource should reset timeout after triggering
Last modified: 2012-01-16 17:42:43 UTC
Hi, currently the timeout for the GSocketSource is only set a single time during initialization but it isn't reset after the GSource was triggered. This makes it necessary to always create a new GSource after triggering, otherwise the timeout would happen even if the condition was met a few times since the GSource creation. It might be necessary to add a new function to create a GSource with this behaviour because old code might rely on the old behaviour.
(In reply to comment #0) > It might be necessary to add a new function to create a GSource with this > behaviour because old code might rely on the old behaviour. No, the old behavior is clearly incorrect.
Ok, will prepare a patch in a few minutes.
Created attachment 205373 [details] [review] Bug 667989 – Reset the timeout in the GSocket GSource after it was triggered
commit d44bb6ef64bf309efa393d8c89138ba23ad6c004 Author: Sebastian Dröge <sebastian.droege@collabora.co.uk> Date: Mon Jan 16 15:49:50 2012 +0100 GSocket: Reset the timeout in the GSocket GSource after it was triggered https://bugzilla.gnome.org/show_bug.cgi?id=667989