aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCharles Kerr <charles.kerr@canonical.com>2013-04-18 10:29:50 -0500
committerCharles Kerr <charles.kerr@canonical.com>2013-04-18 10:29:50 -0500
commitd79745bdb2e9bbd02e162a5209de9f227d1dbbc3 (patch)
tree1abdde58dead84b63e44845b72dc624afd47a7bb
parent033cc134729679757e96715e32e0d517143ef49e (diff)
downloadayatana-indicator-session-d79745bdb2e9bbd02e162a5209de9f227d1dbbc3.tar.gz
ayatana-indicator-session-d79745bdb2e9bbd02e162a5209de9f227d1dbbc3.tar.bz2
ayatana-indicator-session-d79745bdb2e9bbd02e162a5209de9f227d1dbbc3.zip
in rebuild_soon(), add a comment explaining the 500 msec interval
-rw-r--r--src/service.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/src/service.c b/src/service.c
index 2206621..2a10290 100644
--- a/src/service.c
+++ b/src/service.c
@@ -808,6 +808,10 @@ rebuild_soon (IndicatorSessionService * self, int section)
if (p->rebuild_id == 0)
{
+ /* Change events seem to come over the bus in small bursts. This msec
+ value is an arbitrary number that tries to be large enough to fold
+ multiple events into a single rebuild, but small enough that the
+ user won't notice any lag. */
static const int REBUILD_INTERVAL_MSEC = 500;
p->rebuild_id = g_timeout_add (REBUILD_INTERVAL_MSEC,