> > As you can see I’ve experimented with the end date, but seems that > -distantPast works well enough. I’ve also tried forcing a window redisplay on > each pass (as here) but it doesn’t appear to do anything; my understanding > was that the runloop should take care of this anyway. > > What am I missing? >
I wondered about this when you first posted about using a custom runloop mode. I thought window updates were performed only during cycles of the runloop in ‘normal’ mode and so you may not see any actual updates. it seems you do in fact see no actual updates. I am surprised that displayIfNeeded() doesn’t however fix this for you, perhaps there’s something else not getting triggered until the runloop runs in normal mode or else the views aren’t being marked dirty so displayIfNeeded() thinks it’s not needed. Things I’d probably try here are 1) putting the normal runloop mode back to test if your updates now do get shown animated, that will assure you it’s the runloop mode causing it not something else. 2) with the code you have, override a drawRect: somewhere and see if displayIfNeeded() is causing the drawRect:s to be called but the display isn’t getting flushed or if displayIfNeeded() isn’t actually calling the drawRect and other update methods. 3) explicitly invalidate the view(s) to see if you can get displayIfNeeded() to definitely do something. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
