publishUpdate() takes about 500ms to propagate to Dash Clock

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Call publishUpdate() from the extension with e.g. current time
2. Changes are reflected on the UI approx. half a second later

What is the expected output? What do you see instead?
Judging by the systrace, DashClock sleeps for 500ms before processing the 
update request (see http://i.imgur.com/WXxcqDt.png). This is really noticeable 
if extension is trying to show e.g. system time - changes in the system clock 
and Dash Clock are instantaneous and synchronised whereas extension UI lags for 
another half of a second.

What version of the product are you using?
DashClock 1.6.

Which device and Android version are you experiencing this issue on?
Tested on Nexus 5 and Nexus 7 2013 with 4.4.2

Original issue reported on code.google.com by c41by...@gmail.com on 31 Dec 2013 at 1:10

[GoogleCodeExporter]

Working as intended... there's an intentional throttle to prevent thrashing.

Original comment by roman.nurik on 31 Dec 2013 at 2:47

• Changed state: WontFix