On 3/19/09 10:09 AM, Jon C. Munson II said: >I did some digging and found that the real issue is the call for >processPendingChanges that apparently is called via the executeFetch. >According to what I read this is standard behavior. > >So, I'd have to say it isn't a "bug" in this case.
Well, 'bug' can mean many things. :) Months ago, I used a DTS incident on this topic, and was told by DTS that the 'item appearing twice in the table if you fetch in awakeFromInsert' situation (that you saw) is a bug in NSArrayController. I agree with you that it is kludgy to have to use performSelector:withObject:afterDelay:. Such a situation is exactly when you should file a bug/enhancement request. Have you tested undo after switching to performSelector:withObject:afterDelay:? You may find that undo will only undo the setting of the 'auto-incremented' integer attribute. I suspect this is because performSelector:withObject:afterDelay: runs on a different pass through the event loop. -- ____________________________________________________________ Sean McBride, B. Eng s...@rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
