Can you check what's happening on your Communicator by running TaskSpy and check the CPU usage with and without iDesk? If you find a significant difference, I'd like to know.
The only other bit of software I run usually (apart from iDesk) is AquaCalendar. Just installed TaskSpy and checked the CPU load:
I ran TaskSpy (so it was the only thing running) and the CPU load was 0 to 1%
I started iDesk and it settled at 3% with regular, brief peaks every minute or so of 19%
I started AquaCalendar and it settled at 4% with regular spikes at 20%
I exited iDesk and it settled at 4% with no spikes.
Seems to me iDesk must do something every minute or two that causes the spike.
Thanks for testing and posting your results. The reason for the spike is that
iDesk updates it's header every minute. The stupid thing though (which I never thought of before) is that it keeps doing this even when it is running in the background (and noone can see the change anyway).
The version that I will release at the end of this week has this problem fixed. It only updates the header and title if it is running in the foreground. By optimizing the way the header is drawn, the spike has been reduced to 6% (for comparison, pressing a single key creates a spike of about 15%).
__________________
This space intentionally left blank.
The version that I will release at the end of this week has this problem fixed.
Thanks, that sounds good.
One, small, very slight irritation I've had with iDesk is that when I exit another application, I go back to iDesk automatically and it's sitting there with the "Are you sure you want to exit" type message i.e. as if I'd pressed the exit button in iDesk. Sorry I can't give a step by step to reproduce this but I always seem to be in the middle of something when it happens.
This sounds like the CBA-button is pressed twice. I had a report from another user that he experienced the same, but this was due to defective hardware. There was a loose contact in his CBA causing it to sometimes send the keypress event twice.
Another thing that might cause this is the way iDesk checks for events. I had a problem with this before when the About dialog was closed. If this is the cause, then this should be fixed in the next release as well, since iDesk now uses a different (standard) way to check for events (to resolve the CPU-usage issue).
About the CPU-usage: I made one important additional improvement. When the Communicator case is closed, iDesk also stops updating the header and titlebar. Since case-closed events are not sent to OPL application, I had to use a workaround. When iDesk is in the foreground and the case is open (which can be detected) it will check whether the case is open every 10 seconds. If the case is closed, it stops updating header and title.
iDesk 1.45 will be released this weekend.
Best regards
Arjen
__________________
This space intentionally left blank.
Linear Mode
