On 2013 Apr 17, at 09:23, Steve Mills <smi...@makemusic.com> wrote: > But TextEdit doesn't seem to prevent any actual edits from happening, but > instantly undoes each edit. So you see the change for a split second. That's > not a very good user experience. What does everyone else do?
I agree it's weird, but I just let it go that way. I thought, "Apple knows more about user experience than me" :)) > Disable menu items and disallow edits based solely or in part on the > isInViewingMode result? Maybe the thinking is that the user is going to get an unexpected result, one way or the other. Quickly changing it back tells the user that "Yes, we know what you want to do, but you can't do that (change history)". > Does isInViewingMode ever return YES for reasons other than for docs being > browsed in Versions? I found some opposite cases, in Mac OS X 10.7, wherein -[NSPersistentDocument isInViewingMode] would return NO at times when it should have returned YES. My code comments don't give any more detail. Anyhow, I overrode it. If super returns NO, my override double-checks this answer by asking if [[self fileURL] path] contains the component @".DocumentRevisions-V100". Not nice, but it made things work. _______________________________________________ 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
