Hi Parker, It's just as likely something else, but I can suggest two places to look.
One is a constraint that might be triggering a lot of events needlessly. The other is if you are using the drawing api, make sure that the view doing the drawing is in a state where it needs to redraw before performing the redraw and potentially any calculations in there. -Cort On 1/23/07, parkerwhirlow <[EMAIL PROTECTED]> wrote:
Guys, I just noticed that my application is constantly using around 40% of my computer's CPU... I have a decent (albeit old) 2Ghz machine with 2GB ram... This is long after the app has loaded everything and had time to "settle"... Are there any other people out there seeing strange issues where the CPU hangs around 40%? I'm starting into the debugger, trying to break into it while its running to see what is going on... Can't really tell right now. One thing I did see was, the BusyCursor::enterFrameHandler keeps getting called even though I have ended the busy cursor using CursorManager.removeBusyCursor. The busy cursor isn't showing any more either... I don't know how often that enterFrameHandler is called. Could that be part of the issue? Looking for any ideas on how to troubleshoot this too. I have tried to create somewhat simplified applications, but so far none can reproduce the issue I have with the main app. thanks, PW
