Beta 6 -JaPBe- Editor functions crawl with 96% CPU usage

gnozal · Post by **gnozal** » Mon Mar 20, 2006 8:54 am

Randy Walker wrote:I click, wonder if I did because nothing happens, click again and then watch my procedure unfold and then fold back up because the first click was good.

When you fold/unfold all, jaPBe adds a little message in the log, when starting and ending folding, and even the duration in ms, so you know when you are folding and how much time you have lost.

Randy Walker · Post by **Randy Walker** » Tue Mar 21, 2006 1:39 am

I can't get it to duplicate the delay with any consistancy. You know how you can cause a delay in your app by placing a WaitWindowEvent() at the wrong spot in your program, so your app just sits there at that spot until you move the mouse? I get a lot of that type of behavior, but even that does not seem consistant, so I think it may only be coincidental that it resembles the extra WaitWindowEvent() delay. Sometimes I wiggle the mouse and it responds immediately and sometimes makes no difference.

One senario that does seem replicable and also appears to be one of those "extra WaitWindowEvent()" conditions is when I un-fold all and then fold all. Just as it completes the fold all operation it hangs for a few moments on the very last fold. If I wiggle the mouse, it folds immedialtely. If I wait and just watch, it takes a little while, exactly as though it were sitting on top of a WaitWindowEvent() waiting for an event.

gnozal · Post by **gnozal** » Tue Mar 21, 2006 8:54 am

Randy Walker wrote:I can't get it to duplicate the delay with any consistancy.

I always have the same delay (+/- a few ms), sorry.