• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Setting attribute value doesn't dirty the document
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Setting attribute value doesn't dirty the document

  • Subject: Re: Setting attribute value doesn't dirty the document
  • From: James Dempsey <email@hidden>
  • Date: Thu, 16 Nov 2006 10:19:24 -0800

On Nov 16, 2006, at 9:43 AM, Bill Cheeseman wrote:

I've noticed that using accessibility functions to change the text in a Text
Edit window doesn't dirty the Text Edit document or invoke its undo/redo
mechanism. Thus, if the user closes the window, he isn't warned that he's
losing changes. (I haven't yet explored whether this is true of all
applications.)

Should this be viewed as a bug in Text Edit? That is, is it up to
application developers to notice when an Accessibility function changes
something that should dirty the document and set up an undo menu item? If
so, I don't find anything in the existing documentation that clearly calls
out this obligation.

The general philosophy is that accessibility allows an assistive application to discover and interact with UI elements in an application.  Therefore if clicking on a button with the mouse causes a new item to be added, and that is an undoable action - then an assistive application telling that button to preform its 'press' action should do the exact same thing.

Please file the bug against TextEdit as a starting point, it may end up being something that NSTextView needs to do.  (In fact mentioning in the bug that you are not sure if it is TextEdit of the text view that prevents this from occurring would be great.)

Or is there some generic way I can accomplish this remotely from an
assistive application?

Not a good clean way that I know of.  If your goal is to dirty the window to make the warning sheet appear, you could try making some other change via a menu or button, and change it immediately back - but that's just ugly and puts you in the business of making changes the user didn't ask for, and hoping they don't take any actions before you change it back.

-James

-------------------------------------------------------------
James Dempsey
email@hidden
Cocoa Frameworks
 

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
  • Follow-Ups:
    • Re: Setting attribute value doesn't dirty the document
      • From: Bill Cheeseman <email@hidden>
References: 
 >Setting attribute value doesn't dirty the document (From: Bill Cheeseman <email@hidden>)

  • Prev by Date: Setting attribute value doesn't dirty the document
  • Next by Date: Re: Setting attribute value doesn't dirty the document
  • Previous by thread: Setting attribute value doesn't dirty the document
  • Next by thread: Re: Setting attribute value doesn't dirty the document
  • Index(es):
    • Date
    • Thread