Re: undomanger performance
Re: undomanger performance
- Subject: Re: undomanger performance
- From: Martin Wierschin <email@hidden>
- Date: Mon, 02 May 2016 13:10:46 -0700
> My app deals with an object tree that can have millions of leaves. It is possible to run an operation on all of them. Each will register its own change with the undo manager.
Is it absolutely necessary for each leaf object to register its own undo invocation? I don’t know if that’s the actual cause of your slowdown, but it seems like a design to be avoided if possible. Can you instead capture a single undo invocation for all affected objects? Even if you have to bundle up and collect state information for all your millions of objects, having a single undo invocation would likely be more efficient than millions of undo invocations each with their own state information.
~Martin Wierschin
_______________________________________________
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