bzbnd | # 361 | 2011-02-01, 23:37 | Report

Yes , Hi is right

Wonko | # 362 | 2011-02-01, 23:43 | Report

Uhh, my bad...
I reverted the installation procedure to the old one for version 0.15.1 which I just uploaded to extras-devel.
The "Clock & Alarms" entry is indeed a must-have.

Unfortunately, this means for some (those with some custom modifications to "/etc/hildon-desktop/status-menu.plugins") again that Advanced Clock Plugin won't work.
But for the big majority this restores the previous functionality.

Apparently, these are the trade-offs one has to accept.
At least until there is a better solution which applies to all of us.

Mentalist Traceur | # 363 | 2011-02-01, 23:57 | Report

Wonko: Which issue do you mean? The clock applet button disappearing from the menu? No, this update hasn't fixed it. (To be clear, this is the stock button that's in the hildon status menu. That clock applet. The normal advanced clock plugin in the status area still works.) I know I can replace the .desktop files, I can figure that out. Am i really the only one for whom that applet vanished?NVM, I started typing this like 45 minutes before posting, and had massive distractions in between, so in the meantime people had time to answer.

To be clear this is what I meant:

Note the absence of the normal button that you can click to get to the Clock menu. Like I said, I can easily switch the .desktop files around, I'm just wondering if this has happened to anyone else. Also, I'm on the Community SSU by the way. (Clock works just fine though.)

Now, I may have a basic patch for you, to make it possible for a clock style to specify that it is to be redrawn every second even when only minutes are shown (necessary for mine, because I have all the cpu/mem/internet-traffic bars updating every second, but I'm sure other people might come up with clock styles like mine..).

I changed line 165 in /usr/lib/hildon-desktop/advanced-clock-plugin.py from:
to:
And added this under line 37 of /opt/maemo/usr/lib/advanced-clock-plugin/clock.py (moving everything down by one obviously):
Victory. From here all you need to do is add self.force_redraw = 1 in the init area of your clock style, to make it redraw every second. Not extensively tested, but works with all thenormal styles I tried it with (I haven't messed with klingon fonts or the picture-using ones).

- Edit -

You can ignore the first part, I see the issue has been identified already.

---

Last edited by Mentalist Traceur; 2011-02-02 at 00:21. Reason: People posted while I typed.

Mentalist Traceur | # 364 | 2011-02-02, 00:15 | Report

Also wait what?

My status-menu.plugins file was rather heavily modified, and I've never had issues with Advanced Clock Plugin in the entire time I've had it (since you first released it). Did other people with custom .plugins files get messed up before? I don't remember this happening, but even if it did, first-hand evidence of me never having problems says the problem isn't custom status-menu.plugins files themselves, but something specific.

That said, while you're at this way of replacing that .desktop file with this one, can't the future of Advanced Clock Plugin also involve replacing Clocks and Alarms (or whatever) with a better more versatile version? (That's what I thought you were doing at first.)

skykooler | # 365 | 2011-02-02, 01:24 | Report

Are you doing this before the image pattern has been created? Could you post the code you had for that?

Bratag | # 366 | 2011-02-02, 02:42 | Report

For some reason after this update my decimal clocks etc now no longer work/show. Binary still shows up but everything else ... nada, regardless of the settings.

Advice?

Mentalist Traceur | # 367 | 2011-02-02, 02:48 | Report

I think you should be able to combine using the fill option, the font changing, and the font resizing, to get exactly the equivalent of the default clock. Or something very very close.

- Edit -

Now that you're shipping images in with the clock styles, perhaps we can make even more optification? I mean, the images don't need to be in rootfs, right?

BTW: Since I let the latest update to it's thing, Wonko, I see that it fixed the Clock and Alarms status menu button with the new update. So just some verification for you, it should properly revert back for them.

Now that I've figured out how to do this keep-updating-clock thing, I'm probably within a day or two of spare fiddling time to releasing the clock style I've been working on for like two months now. It's a bit abysmal how long it's taken, but hey, I went from someone with no coding ability to someone who can actually sorta-kinda do basic Python stuff.

And all thanks to you, Wonko, for liking my original 'make your status menu binary clock have the option to show normal numbers too'.

---

Last edited by Mentalist Traceur; 2011-02-02 at 02:59.

porselinaheart | # 368 | 2011-02-02, 04:07 | Report

hmmm. made some test images for a flipclock, worsk fine, but the seconds digits are not cycling, they're just static. anyone have advice??

Wonko | # 369 | 2011-02-02, 08:46 | Report

I'll add an according modification.
Though, I'd prefer to use a boolean variable, so you would use "self.force_redraw = True".
I think for the time being, it should be ok if this is not set via the settings ui but is set only by clock styles needing a refresh every second.

Good to know.
Thanks for the info.

Actually, it is optified.
"/usr/lib/advanced-clock-plugin" is a symlink pointing to some place in /opt.

Well, as it didn't work out the way I wanted I discarded the code.
I could add it again and add an option to the settings UI for it.
By the way, what do you mean with "creating the image pattern"?
The code for playing the animation is in "/usr/lib/advanced-clock-plugin/pixbufanimationplayer.py"

As usual, run (as root):
to see what's going on.

Edit:
Well, I am currently not planning to do this.
I am already very short of time and this project would really blow my schedule.
Having said that, my schedule is already tight enough.

---

Last edited by Wonko; 2011-02-02 at 08:58.

Mentalist Traceur | # 370 | 2011-02-02, 09:06 | Report

Yes, I agree, it doesn't need to be a settings thing - not the way I ended up implementing it (if enough clock styles arise that have this optionally, it could be useful in settings, but until there's heavy demand/need for it, it's fine being manually set in code by the clock style).

And I also agree with you on the True/False thing. I just screwed it up as a boolean initially when I figured out how to do it. (I used "true" instead of "True", which caused errors, and I wanted to make sure it worked at all, so I didn't fiddle too much with figuring out the right way of doing it. The post you just made cleared that up though.)