View Single Post
Nathraiben's Avatar
Posts: 267 | Thanked: 408 times | Joined on May 2010 @ Austria
#131
Originally Posted by Rob1n View Post
I think it was just malformed XML last time I had it happen. That certainly should be preventable (or at least less likely to happen) using an app than manually editing.
Thanks, that's quite reassuring. I more or less just copy the hildon.menu from the application's resource files to the menus folder, so this really shouldn't happen at all.

The only files I'm dynamically messing with are the .desktop file (an error within which only seems to result in a default icon) and the .menu files in the submenu folder (and messing up those will simply make Hildon not import them).

Originally Posted by zoner View Post
very interested to see how you come out with this.

I've setup my app launcher with folders just the way I like several different ways, but any time i mod hildon.menu, cpu usage ramps up to about 4% at idle. No big deal, but it pulls on the battery overnight.

guess i can make some "Good-Night" and "Good-Morning" scripts but it shouldn't be that way.

are you far enough along to see if this bumps up hildon-desktop activity at idle?
I'm just automating the process explained in my tutorial post, so I can already see the results, which so far are:

Almost no idle CPU usage (with X Terminal active, Hildon keeps between nothing and 1.5%, with stray peaks at 2%), the only effect I can see so far is that sometimes there's a delay in loading the application menu itself. For a second or two, it will show the no-applications-found message.

I've included a deactivate (the one that for some strange reason at 2:30AM I named "unactivate" ) button that will simply delete the hildon.menu file, so if you still find the hildon.menu messing with your CPU you could just deactivate it at night and hit the activate button first thing in the morning.