Setting attribute value doesn't dirty the document
Setting attribute value doesn't dirty the document
- Subject: Setting attribute value doesn't dirty the document
- From: Bill Cheeseman <email@hidden>
- Date: Thu, 16 Nov 2006 12:43:50 -0500
- Thread-topic: Setting attribute value doesn't dirty the document
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.
Or is there some generic way I can accomplish this remotely from an
assistive application?
--
Bill Cheeseman - email@hidden
Quechee Software, Quechee, Vermont, USA
http://www.quecheesoftware.com
PreFab Software - http://www.prefab.com/scripting.html
The AppleScript Sourcebook - http://www.AppleScriptSourcebook.com
Vermont Recipes - http://www.stepwise.com/Articles/VermontRecipes
_______________________________________________
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