Re: N900 clock replacement [continued]
 

@ade
I have problem with worldclock - I`m using thumb version (don`t know if is it the newest, installed it the same day when You published it). Adding new alarm doesn`t work anymore - worldclock closes immediately, when clicking "Date" button on "New alarm" dialogue. Running it from xterm outputted "Illegal instruction".
Is it only my device (I`m using latest CSSU-thumb) or not?

Re: N900 clock replacement [continued]
 

I do not experience issues myself, otherwise I would have done something about it :)

Please make sure you have the latest version downloaded first.
I am using the thumb compiled version with date function on an almost daily base, but other than that I don't think this version is thoroughly tested by others. Setting an alarm not using an explicit date does still work?
Let me know if you still have the crash using the latest version...

Re: N900 clock replacement [continued]
 

To be 100% sure, I just downloaded/installed/rebooted (1 minute ago) this version: Thumb version worldclock with date support (for thumb2 supported kernels) from here http://dl.dropbox.com/u/42147901/wor...ture_thumb.zip - so I have (and had - judging from date stamp and file size) running the latest version.

Problem is still here - every time I use "Date" button in "New alarm" window (doesn`t matter how that window it is invoked), worldclock is instantly terminated.

PS - creating new alarm without changing its settings (so with current date and time) works, adding name too.

Re: N900 clock replacement [continued]
 

yep, I can reproduce it with Polish regional settings.

edit:
Can't believe how sh*tty and inconsistent maemo is at times :mad:

All the languages I tried return me something like "Saturday 27 October 2012" when I request a long date. But no, in Polish I get "sob 27.10.12". Not really a long date format, is it? Once I set another language for the format itself, I get a polish date like "piątek 26 październik 2012". But that is by using a Qt method, which I can't use, because it determines it's language by looking wrongly at the regional settings, not the device language. Sigh...

Re: N900 clock replacement [continued]
 

Hey, guys, where - while creating new alarm - is "date" option? I'm using polish settings too, yet I have never been able to run into it - it seems, that I must have avoided this option all-together.

when I open "new alarm" window, I can only change repeat settings (days of week, when alarm should be repeated), and it's working fine. What I'm missing?

// Edit - strike that, I was using wrong version (one without alarm on date support).

/Estel

Re: N900 clock replacement [continued]
 

I have now also been testing the "with date version" with Polish, Russian, Czech and Spanish (next to Dutch, French and English UK/US).
Had to fix some things with Polish, Russian and Spanish; that is the disadvantage if you rely on literal strings :p

Just updated the "worldclock_incl_date_feature_thumb" version for that.

edit: German, Portugues, Danish, Norwegian and Italian also look okay. Swedish fixed

@artpra, could you try the new version?

Re: N900 clock replacement [continued]
 

@ade,
it works!

One suggestion though: when setting an alarm in clock app, we are thinking about an alarm to set on about some hours or few days from now, not months. For long periods of time (weeks and months), we use calendar app, with much more options for each entry.
I want to say that new alarm date settings should be "days-focused", not "months-focused" and therefore I suggest to change date button description (in "New alarm" dialogue) from "mon, 1 november 2012" to "monday, 1 nov 2012" if it`s possible of course.
It will give more space too - now polish date description barely fits to button/screen ("śro, 31 października 2012").

Re: N900 clock replacement [continued]
 

When I introduced "setting an alarm on a specific date" in the replacement clock, I anticipated some reactions (either negative of positive). Having received virtually non of them, it does not seem an option people are waiting for. Perhaps people are already used to enter these kind of alarms in the calendar app or use Alarmed for that.
As it was an option I wanted myself, I would have added it myself anyway. But it does imply I more or less see this version as a personal fork now, extended for my personal preference. In that context, I am fine with it's current state, and one can try it if he or she sees any usability in it.
Of course I still do want (to try) to fix real "showstopper" bugs if found.

Re: N900 clock replacement [continued]
 

Sorry I did mean to reply but TBH I have never really needed to use this feature since I installed it.
I have been so used to Calender for date events, and alarmed for repeat events, IAH I doubt I would use it.

However, I do not see why you would need to fork.
The feature is useful (to some) and does not alter any default behaviour.
I would be fine with it being a permanent feature of worldclock.

Re: N900 clock replacement [continued]
 

Same here - it's ncie feature to have, that doesn't block or restrict "stock" features (even if it don't use it, personally - yet, probably due to habits).

I don't see much reason for keeping two separate versions or worldclock (4 if you count thumb) - not much reason to not install the most "augmented" one.

/Estel