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 659738 - Need a way to tell GSettings to delay writes for rapidly changing properties
Need a way to tell GSettings to delay writes for rapidly changing properties
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: gsettings
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Allison Karlitskaya (desrt)
gtkdev
Depends on:
Blocks:
 
 
Reported: 2011-09-21 15:51 UTC by Rodrigo Moya
Modified: 2013-10-24 19:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Rodrigo Moya 2011-09-21 15:51:06 UTC 
When binding GSettings keys to rapidly changing properties (like "value" on GtkAdjustment's), a write is performed for every change.

Talking with Ryan, he suggested having a flag (_RATE_LIMIT) to allow apps to specify writes to be performed somewhat delayed, or maybe apply the rate limit by default and have a flag to turn it off.
Comment 1 Allison Karlitskaya (desrt) 2012-01-19 02:05:23 UTC 
i started implementing this, but it's slightly weird -- the app could exit while rate-limited changes are pending and there's no good way to force them through.

it could be done in the backend and g_settings_sync() could write them... or it could happen in the front end and g_settings_sync() is taught about it then.
Comment 2 Allison Karlitskaya (desrt) 2012-01-19 03:54:47 UTC 
bug 468121 suggests what could be a better way forward.  integration of this sort of thing into various widgets would substantially improve our ability to make intelligent decisions about the correct time to do writes.
Comment 3 Allison Karlitskaya (desrt) 2013-10-24 19:34:10 UTC 
This problem is substantially solved.  We never have more than 1 or 2 writes queued up at a time now.