On 22/08/2013, at 9:43 AM, Shane Stanley <sstan...@myriad-com.com.au> wrote:
> Not that I can see. Unless… I suggest logging 'self' at the point you set up your undo. If you can trigger the bug, then this will tell you what the real object responsible for the exception is - at the moment NSProxy is hiding it from you. > The process takes a fair amount of time -- it could even be a minute or more > -- so I'm doing it on a background operation queue. Only if that first part > goes fine do I update the UI with the result in an undoable fashion, using > the above. I'm not sure there's a better way. Maybe post the code that's in the block - someone might spot something iffy. --Graham _______________________________________________ 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
