Re: Coalescing Messages From Continuous Controls
Re: Coalescing Messages From Continuous Controls
- Subject: Re: Coalescing Messages From Continuous Controls
- From: Nick Nallick <email@hidden>
- Date: Fri, 5 Dec 2003 17:07:50 -0700
On Dec 5, 2003, at 3:49 PM, Jonathan Wight wrote:
If the effects of the housekeeping are visible to the user then why
not use the undo manager directly?
They're not visible to the user. It's more a question of keeping track
of changes for use elsewhere similarly to recording an AppleScript. I
need to throw away all of the redundant messages and just keep the last
one, but it's hard to know when the last message occurs.
Of course it might be a little confusing for the user to see "Undo
Housekeeping" in the Edit menu so you might want to think how and when
you post your undo action.
I don't think this would work for me anyway. My understanding is that
the undo manager marks the undo stack before and after the event is
handled, then an undo causes everything on the stack between the marks
to be called. If I put something on the stack it won't be called
unless undo is executed, but I'm looking for a way to run a function in
the same time frame as when the undo manager puts the second mark on
the stack.
Nick
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.