Understaing NSNotificationQueue and IDLE
Understaing NSNotificationQueue and IDLE
- Subject: Understaing NSNotificationQueue and IDLE
- From: Francisco Tolmasky <email@hidden>
- Date: Thu, 24 Apr 2008 02:26:36 -0700
It has often been asked on this mailing list how to get undo working
with continuous controls, and the generally agreed upon answer seems
to be to use NSNotificationQueue to coalesce notifications under
NSPostWhenIdle. In fact in a previous thread it was said that this
method would work whether or not continuous controls were implemented
using modal event loops (that is, instead of using mouseDown/dragged/
up). My question is whether this is really true. From playing around
with this, it appears that the only reason the runloop isn't "idle"
when holding a slider still is that the loop is eating up all the
events, while if I mouse down and drag in other parts of the window
"idle" notifications are indeed sent. Does this mean that using the
NSNotificationQueue method would break if Apple every chose to use
mouseDown/dragged/and up instead of just setting up a modal event loop
on mousedown?
Thanks,
Francisco
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden