Notices

wow, the developing is moving fast: I love the neverimplementedbefore slide up and down animations and the mesmerizing night light tones (I remeber J suggested that many posts ago )
I don't dare to touch the code before jolouis don't think is ready: he keep adding features and fixes!

Didge, if you run the clock from x-term window and look at the output, do you ever see anything that say "on_battery" or "charging"? The code is setup so that if you have the charger attached it will keep updating the digits, but if you run on battery it does not update unless tablet is active. I'm going to add a "all night" option that makes the tablet stay in the "dimmed" mode while the clock is running (whether connected to charger or not), but that won't have anything to do with the updating as in that state it should update all the time anyways... Has anyone else run into the non-updating with charger attached thing?

I'm just trying to clean up all the bugs that people have reported and cram the last few features in... the animation thing wasn't intended to be there, but since I'd been working on it and had to use my updated code to fix the bugs I ended up finishing that up and releasing it as well rather than trying to keep it hidden ;-) Sounds like we're getting really close to a good full release candidate though, so once that's done then Ciro can go nuts with things and we'll start the process over again to get the next version going!

I have a version of flipclock installed, but I've never really used it. Strangely, I woke up this morning and somehow flipclock and launched on its own. I'm fairly sure I did nothing to launch it between putting the tablet down at bedtime, and picking it up again this morning.

Anyway, glad to see that this project is humming along nicely.

lm2, it sounds like you had an alarm set that you forgot about; if you go into flipclock and check the alarms page, see if any of them are "green" (enabled); they will cause the app to automatically launch when they occur.

I tested it again, looks like you need a third state. :-)
Charged!
That explained why it worked in the morning (wasn't charged for a day) and stopped working later (when it has finished charging).

lol, the flipclock self promote himself: time to begin to be scared

Okay guys, got everything fixed up again... so changes:
- Fixed charging/battery thing, that was some code that I borrowed from Kagu that was listening to the wrong signals; anyways, should be all resolved now
- Added Dbus dependency to deb file to prevent errors like yukop4 ran into.
- Added new "allNight" mode, where clock will keep the screen in "dim" mode all the time when running rather than letting it turn off completely.

Now here's the catch... I've run out of space on the interface for the switch to turn that "allNight" feature on or off! Right now the feature is on by default, and you can manually update the config file.. but a switch or controller would be good right?? Or is this not really a big deal for people at the moment? Once I get this sorted out and we confirm there aren't any other issues I'll push to extras-devel for a full release candidate...

It is kind of scary. I set an alarm to test this out (after finally figuring out how to get to the alarm page). Set a time, turned alarm on, wait. The alarm sounds OK and I push the snooze button. But not wanting to hear the alarm again, I turn alarm off, and then exit the program. Sure enough, after 10 minuites, the app starts and the alarm sounds again. I checked the settings and alarm is still turned off. So I set the alarm time back to zeros and turned alarm on and then back off, then exit app. Same thing - app starts by itself and alarm goes off.

Next time I exit app and power down N810. Guess what - after 10 minutes, N810 powers up by itself, FlipClock starts and alarm goes off.

Help

CDR, yea that's a short comming of the snooze option the way it's done right now... just wait for the clock to open up at the alarm, and press on the clock digits themselves (instead of the snooze bar at the bottom) to cancel the snooze completely.
I was thinking about making it clear the snooze if you exit the clock; does that make sense guys? I mean I could always add another button somewhere to "Cancel snooze", but then have to find somewhere on the interface for that and there's not a lot of space... the downside to the clear snooze when exit would be that if you hit snooze and happen to close the app for whatever reason, no more snooze... but I don't think that's a very likely scenario...

Thoughts?

Okay, snooze by default is now handled internally; so if you exit the app after hitting snooze, it gets cancelled. (and for anyone who wants to keep snooze the old way, it's just a config setting in the flipclock.conf file, so easy to change either way). I think we're going to need a second page of config options at this rate lol... one for alarms, and one for actual clock settings... along with some instruction or help thing on the main screen to show people how to change screens...