Anyone noticed that a repaint request may take a long time to be honored? Like 40-50 seconds?
I am wondering if I have bombarded the queue with too many repaint()…accidentally…
Any other reason a repaint request may get delayed?
Thanks…
Anyone noticed that a repaint request may take a long time to be honored? Like 40-50 seconds?
I am wondering if I have bombarded the queue with too many repaint()…accidentally…
Any other reason a repaint request may get delayed?
Thanks…
40 - 50 seconds?!?!?!?
You mean 40 - 50 milliseconds, right? At least I hope so.
Repaints are handled by the main UI thread. The same thread that is calling startApp(), pauseApp(), commandAction(), keyPressed(), keyReleased(), etc. If any of those methods take a while to return, the repainting of the screen will be delayed.
I doubt that many repaint() calls will have the same effect because they probably get “united” into one call (ie, the last repaint() is honoured, the rest not). Unless you are calling serviceRepaints() after each repaint().
shmoove
[quote]“united”
[/quote]
I prefer Suns term coalesced, but its an absolute bitch to spell when you are using it often =D
I think something got screwed up by between Windows the Emulator, and the IDE.
I reran the tests the next day, and everything worked as expected!!
;D