Notices

Could be.
My N810 has been slowing down the last few days.
Rebooting cleared it up. Didn't check mem first.
Haven't installed anything lately except this and Advanced Status Bar App.

I have also experienced this. Recently installed Statusbar Clock and the Advanced Backlight Statusbar applet so expecting it is one or the other causing the problem.

Everyone having a slow-down after installing statusbar clock:

It is very likely there is a memory leak in the application. My c memory management is a bit hazy, so if anyone could take a look at the code and let me know where I should be free'ing variables, that would be great. I assume it is in the update function, as that is the one getting called all the time. I will take a look.

k. well the only reason i noticed my memory decreasing is because of the load applet. its usually maintained at one bar but stared increasing to 2 with nothing open then 3 last night.

i checked the processes and turned out hildon-desktop was getting quite large so i decided to disable the clock. hildon-desktop crashed after i hit ok. the rest of the system didnt crash because the power button still brought up that menu allowing me to lock the machine or power it off. the screen lock toggle also still worked.

give it a couple of days and ill see if i still have an issue with memory. could be my imagination and that anything i did woulda crashed the desktop.

gluck, hope we figure this one out soon...

Yea, I noticed the memory use of my desktop process ballooning to the point that the tablet was barely useable. I didn't think about the possible causes but it must be the clock since that's the only thing I've installed recently that runs in the background.

Edit: Damn...I also installed the statusbar app for brightness/volume recently, so I can't say for sure which it is.

I don't think its your imagination, and at the same time, I don't know that I want to blame my slowdowns on the StatusBarClock either. But it just might be that the addition of this applet might have exposed an issue in the statusbar itself. Just a thought.

I have uploaded a new version (with a big version bump) to my garage page.

Essentially the only added feature is "stacked" mode which is selectable through the configuration dialog. The rest of the changes are cleaning up the code a tonne - getting rid of duplicate functions between the plugins by using dbus to communicate.

Using dbus is a much smarter way to go compared to my old method and eliminates quite a bit of CPU usages. Essentially the hour plugin is called to be updated once an hour instead of 3600 times an hour. Or course, it also gets called any time you change a configuration option.

As for the memory leak, I found a very unsmart typo (gchar* hours[4] instead of gchar hours[4]) that I think may affect memory. If anyone has a good tutorial or rule of thumb as to when I need to free memory manually versus when the program will do it for me, I would appreciate it.

I will update the first post in this thread with the new release details.

thanks for the update

Question: Have you thought of making a version that takes up just one location in the status bar? So it has a smaller font so that hh:mm fits in one space?

I think, as the chief architect and grand poobah of the wonderous 2008 Statusbar Clock, you should put your garage page link in your sig.

You should crow about it and let others be in awe of it; it's a very good piece of app.

Also. I forget where your garage page is a lot... .

To add my 2 cents on the UI... What about getting rid of the 3 options when you click on the time and just have the date (if you click on it - it takes you go to the clock application) and have 24 hour mode in the configure menu. Most people don't need to quickly switch between 24/12 hr mode. With these changes if you click on the time you see the date and configure only.