Re: N900 clock replacement [continued]
 

Also found some bugs/features missing from original clock.
Just switched to worldclock on my testing N900 so I can compare both clock apps side by side.

Bug?
If you switch off automatic update and change the time manually, then Save; the application crashes.

Bug?
Even tho I have set the location to London, World Clocks shows Local time as Cardiff.

Missing?
Non-local items in World Clocks cannot be clicked on to show World Clock Details including the map etc.
Also clicking on Local time in World Clocks should resolve to "Adjust Date and Time"

Missing?
The glow around the buttons on clicking is not there.
Useful to provide positive feedback of pressing the screen/button.

Missing?
When setting alarm the original version remembers your last alarm time, worldclocks always shows current time.
(Not a problem for me)

Missing?
When selecting repeat in alarm original version shows full day name 'Wednesday' where as worldclock shows 'Wed' for example.
(Again not a problem, just looks odd when you are used to the original)

Hope this helps.

Re: N900 clock replacement [continued]
 

Your are right.
Some how, in my memories, the font was always Nokia Sans.
But that is not true. Not in the stock clock and was not in the replacement clock. It should indeed adapt to the theme font.

I will revert this change later.

Re: N900 clock replacement [continued]
 

I cannot reproduce this...

I can set London or Cardiff and do not see a difference with the stock clock for that matter. Can you give some additional info?

The absence of the map has been mentioned before. It won't be included by me. The details screen is also absent. It does not add much extra in my opinion, as does the possibility to click on localtime in the worldclock screen.

I think it is harder to achive in QT. Not my intention to change this.

I think the replacement clock approche is more convenient. The last alarm time not interesting most of the time, often you want to set an alarm an hour or so from now.

The stock clock uses full daynames, and as soon as too many days are selected for repeat, it switches to short daynames. The replacement clock always shows the short daynames. I think you will get used to that soon. I could have a look at it though.

And before it is reported as a difference :) : the replacement clock also shows the year in the worldclock screen, the stock clock does not. Also: the stock clock shows a clock picture with the time in the worldclock screen, the replacement clock does not.

It is not going to be a one on one copy of the original, but should have a very comparable experience in my opinion.

Thanks for your report, sixwheeledbeast.

Re: N900 clock replacement [continued]
 

Upon first installation last night I reproduced this 6/6 times, now I can't make it happen I have no idea why?

Although in addition I have noticed if you select your timezone from adjust date and time and click done then save the application disappears to.

Anything I can do to to help solve let me know

See Screenshots
The default clock only shows local time but I like your feature.

Agreed

Shame I think it makes a huge difference, but I understand.

Agreed

Cool, did notice that they go short when not enough room.
I could get used to it, if not changed.

I understand. It is nice to have a fresh tester look over a project. The comments were meant to be constructive :)

I was only pointing out missing items not changes/extra features.

Not bothered about the little clock picture, never used it so didn't realise it was missing.

Anytime :D

Re: N900 clock replacement [continued]
 

timezone change:
What I do see is that the replacement clock goes to the background then a new timezone is choosen. But it does not crash or something.
If you can reproduce a crash, see if there is any terminal output after starting the clock using /usr/bin/worldclock

cardiff/london timezone:
I can reproduce it now. A bit odd, but the timezone itself is the same (for now). Gonna have a look at it.

Re: N900 clock replacement [continued]
 

Thanks all lot.

The timezone issue doesn't crash, it get minimized as you say.
Sorry if I didn't explain that correctly.

This is different from the issue when changing the time.
Annoyingly still can't reproduce it.
I will try to reproduce this run from a terminal if possible and let you know to output.

Oddly it's not just Cardiff my Local time is now London on one and Belfast on the other.
This happened after changing to USA time closing the application and then changing back to London.
It's something to do with the City's in this same timezone as London?

Re: N900 clock replacement [continued]
 

The local timezone city issue should be tackled.

The replacement clock choose the local city based on the current timezone.
In case of timezone "Europe/London", it matched 3 cities (Cardiff, Edinburgh and London itself), and would pick the city first alphabetically.
I now base the local city on the info stored in gconf (based on city-id).

Will revert the theme font change and look at some other things addressed in the comming week. But if you want to test the local city fix, the downloadable file is refreshed.

Re: N900 clock replacement [continued]
 

Thanks that's great.

I have a request if possible.
Any chance of having UTC as a timezone in world clocks?

Re: N900 clock replacement [continued]
 

I once introduced it :) :
http://talk.maemo.org/showpost.php?p...&postcount=100
And then I reverted that for reasons mentioned here:
http://talk.maemo.org/showpost.php?p...&postcount=105

Re: N900 clock replacement [continued]
 

I'm experiencing a strange problem.
Even though the hour is 10:44 right now, N900 shows 8:44.
What's more every city in the world seems to be GMT+0 (London), no matter whether it's Warsaw, Kyiv, London, Brasilia or Honolulu.
I'm using libc6 2.10 from this thread: http://talk.maemo.org/showpost.php?p...&postcount=105