this is a very nice idea. I don't have any time in the moment. But if I have some, I will add this (and the lithuanian translation).
Please feed me with some free to use images (the one you used are very nice!). Size 96x96 and png or ico is perfect.
Hello all. I've searched the thread numerous times over the course of the past two months to see if someone else has seen this... but has anyone else noticed this app taking 100% of the CPU when it is in the foreground?
My device: CDMA Touch Pro2
ROMs: Energy's Cookie (Energy.RHODCDMA.23569.Sense2.5.Cookie.Jul.10.7z is the latest I've tried it on) - but I've been trying it since the May ROMs
Monitoring application: BattClock, with one stripe (or even an actual percentage counter) showing the CPU utilization
I've tried TouchWatch since v2.4 (2.42 and 2.43) on about a half dozen Energy ROM versions, and when this app is actively running a timer or stopwatch, the utilization pegs 100%. If it goes in to the background, utilization drops to "normal" levels.
I've run SPB Time, G-Watch, and a slew of other timers/stopwatches and none of them use more than 50% or so of my CPU when painting the screen in the foreground.
Now, please no flaming... this could be because of the custom ROM I am running, etc. Just asking if anyone can validate this on other models or TP2 ROMs out there. Next time I flash, I might put back my stock ROM + battclock and see if this still happens. Note I doubt this is due to some issue with BattClock (2.1.2) as I've never seen this with any other stopwatch app so far.
If this has been discussed elsewhere, I apologize and please redirect me to that thread.
Hello again : )
I think that can be useful to highlight active OR to shadow inactive timers:
Just two additional reg values: InactiveTimerColor and ActiveTimerColor.
Existing variant can be achieved by setting InactiveTimerColor & ActiveTimerColor with the same value.
|Thread Tools||Search this Thread|