Re: Re: App crashes when voice over is turned on
Re: Re: App crashes when voice over is turned on
- Subject: Re: Re: App crashes when voice over is turned on
- From: "Tom Harrington" <email@hidden>
- Date: Thu, 14 Sep 2006 13:06:28 -0600
On 9/5/06, James Dempsey <email@hidden> wrote:
I am guessing that you probably have written some sort of exception handler
that overrides the standard AppKit behavior.
The accessibility infrastructure in AppKit uses exceptions internally, and
therefore if you are doing something special with every exception raised in
your Cocoa app, you will encounter the issue you are seeing with users that
turn on VoiceOver or other applications that use accessibility (AppleScript
GUI Scripting is another example).
If you have some sort of custom exception handler, you should check the
exception for the prefix "NSAccessibility..." and allow those exceptions to
proceed in the default manner.
Pardon me, but this seems to imply that writing an assistive
application is more or less guaranteed to be a mine field. If some
unknown third-party application implements this kind of exception
handling, then any assisitive application will potentially cause it to
crash, even though neither application is doing anything contrary to
documentation?
Is there any way an assistive application can determine that this is a
possibility, and avoid making calls that could cause other apps to
crash? Or is the only option to contact the developers of these apps
and ask them to please filter out accessibility-related exceptions?
--
Tom Harrington
email@hidden
AIM: atomicbird1
_______________________________________________
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