Notices

Wow the application really changed:
Im impressed: beside the DBus related "One moment" seem everything snappier than before. Ill play with it a bit and begin to take a look of new code . Everything make sense but the the alarm setting is begin to became a bit confuse: when the actual day alarm is disabled it should show the alarm enabled for next day. I had same issues when I tried the 7+1 alarm solution. I dont want get tricked by an alarm clock .
Do the setted alarm should show up on the nokia alarms? I have no idea how dbus manage them. I REALLY hate the standard 'Open file' dialog I could make a fork using the interface I made for the synesthesia audio player (It also give a way to test the audio level).
I let you optimize the things but it already look great.

Installed it, launched it. Still getting "Can't read user wallpaper" popup. Also getting "Ca't read config", crashes after that and closes. It appears to crash at line 73 in flipclock.py, invalid parameter.

Any ideas?

Ok. Got it to run. Froze on enabling alarm (1+ min), killed it manually. Runs fine now, alarms enable ok. No more warning about the config file. Still can't read my wallpaper, o well.

Commented the following line in flipclock.py :
ci.device.set_device_state_callback(ci_eventHandle rs.deviceStateChangeEvent, system_inactivity=True, user_data=None)

Don't know what it does, but it crashes if I uncomment it.

Other than that, looks great, I'll play more with it late.

Thanks, I new there'd be some problems and things... I'm going to play with this on my other tablet (fresh Diablo install) to see if I can reproduce some of the errors. The line most people have had problems with (line 73 in flipclock.py) is what setups the "stop doing anything when the tablet is idle"; it's not 100% critical to operation of the clock, but does help a little with power management/etc. Works fine on my tablet here and obviously Ciro didn't have issues, so maybe it has to do with a bug in the version of Python or OS2008 that you have installed? Would somebody mind trying updating it to read:
ci.device.set_device_state_callback(ci_eventHandle rs.deviceStateChangeEvent, system_inactivity=True)

And see if that makes any difference? Again I'll try here and see if I can reproduce the error...

Ciro:
"Everything make sense but the the alarm setting is begin to became a bit confuse: when the actual day alarm is disabled it should show the alarm enabled for next day" - Yea right now it just looks for the alarm that's set that day; I couldn't think of how to show what day the alarm was set for, so I figured showing for the current day was okay, though it should really go gray out once the time of that alarm has passed... If you can suggest a better way (visually) of showing the next alarm, I can roll it into the code no problemo.

"I REALLY hate the standard 'Open file' dialog" - yea me too, it was a bit of a last minute toss in because I was more focused on getting sounds to play and things than actually how to choose them. I figured this was a good "Temp measure" until we could merge the concepts and stuff you had from your Youamp Media player thing there into the clock.

Still some bugs and lots of room for improvements!

I saw someone ask about this earlier. I'd love to have the option of dimming or keeping the clock screen up. Pycage has managed to make MediaBox defeat the tablet screen saver so that it does not go dim while playing a song or video. I don't sleep well and look at the clock a lot.

Flipclock is visual eye candy with utility.

The ability to keep the screen lit is quite easy to include; I was contemplating putting it in there while the alarms were actually going off. For a long term thing though (i.e. overnight) the best option might be to have it only keep the screen illuminated if the charger is attached? I know there's an option in the display settings for this, but it shouldn't be too hard to do from within flipclock... my only fear in doing it without charger all the time would be that the battery on the tablet might get drained quite quickly if the display was set too bright for example, and then the clock would become quite useless ;-)

I'm a little concerned about the people saying that the device state code is failing though, so I want to try and get that resolved first. I did an clean install from the deb on another tablet and could not reproduce the problem at all (it worked just fine, though I have to remember to take that "can't read config" message out since the config file is generated by default when you launch the first time...)

Anyone had any more details/information/luck about the deviceState problem that's been reported?

flopclock has wallpaper issue then crashes immediately

also got pygame from solarwolf as pygame download from this thread would not load--it all worked with previous version

Okay everyone please try again, I've updated the deb to include a small work around for anyone who was having osso crashing problems. If you had any other strange issues or unexpected things you need to make sure:
1) You uninstall flipclock (latest version, or any version)
2) You manually remove /home/user/.flipclock.conf
3) RE-install the latest deb by following the link on the garage page:
https://garage.maemo.org/frs/downloa....1.5_armel.deb

Lemmy, update to the latest deb following these instructions, then run flipclock from a terminal and let me know what the output is; I've added some extra debugging lines to help try and troubleshoot your wallpaper problem there...

flopcock now install-no bugs so far