From: Thomas G. <th...@gs...> - 2011-06-21 11:32:32
|
On Tue, Jun 21, 2011 at 00:01, Carsten Haitzler <ra...@ra...> wrote: > On Mon, 20 Jun 2011 19:37:50 +0200 Cedric BAIL <ced...@fr...> said: > >> On Mon, Jun 20, 2011 at 6:26 PM, Eduardo Lima (Etrunko) >> <eb...@gm...> wrote: >> > On Mon, Jun 20, 2011 at 1:23 PM, Eduardo Lima (Etrunko) >> > <eb...@gm...> wrote: >> >> Hmm. I found a weird behavior with the clock after noon and 24h mode. >> >> Screenshot attached: >> >> >> > >> > Damn, hit the send button too fast. Forgot to add that it happens only >> > at when you click on the clock and the popup shows. The next update of >> > the clock it will display the time correctly. >> >> Yes, it seems like hour are not updated correctly the first time. >> That's another bug not related to the wrong one we repported this >> morning (or maybe that was yesterday afternoon for Raster). > > as i keep saying.. i can't reproduce it. it's workign fine here. > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > The Rasterman (Carsten Haitzler) ra...@ra... > The wrong-hour bug is easily reproducable. Use systemclock with UTC + local timezone, turn off seconds display, turn on digital 24h clock (it only affects digital 24h) and open the calendar-popup. It will show UTC, not localtime, while the main clock will show localtime. Turn on seconds display, it will show UTC on the popup again, but after 1 sec, when the clock gets updated the hour gets set to localtime. It also affects the main clock (not popup) itself, but of course only after a E (re)start. I did take a quick look at the code, but didn't find the reason. Though you know the implementation and will probably spot it right on. The reason certainly has to be the timezone-difference that's calculated after updates, not at load time. |