FROM : John Stiles
DATE : Thu Mar 06 02:12:52 2008
There are many times in my code where I want to defer a selector's
execution until the next time the event loop runs, which is a perfect
match for -performSelector:withObject:afterDelay:, passing a delay of
0.0. However, this executes after the app has repainted all the windows.
Is there a way to get a selector called later, but before windows paint?
Right now in my app, there are some controls which appear and then their
state changes a fraction of a second later, and I'd like to avoid the
visually jarring "pop" effect of a control which changes itself right
after first appearing, but I can't find an easy way to avoid deferring
some operations.
DATE : Thu Mar 06 02:12:52 2008
There are many times in my code where I want to defer a selector's
execution until the next time the event loop runs, which is a perfect
match for -performSelector:withObject:afterDelay:, passing a delay of
0.0. However, this executes after the app has repainted all the windows.
Is there a way to get a selector called later, but before windows paint?
Right now in my app, there are some controls which appear and then their
state changes a fraction of a second later, and I'd like to avoid the
visually jarring "pop" effect of a control which changes itself right
after first appearing, but I can't find an easy way to avoid deferring
some operations.






Cocoa mail archive

