Re: kAXErrorCannotComplete timeout longer in Panther?
Re: kAXErrorCannotComplete timeout longer in Panther?
- Subject: Re: kAXErrorCannotComplete timeout longer in Panther?
- From: Matt Gough <email@hidden>
- Date: Tue, 04 Nov 2003 15:09:32 +0000
>
> In some very rough testing (ie.counting One-1000, Two-1000 etc) it seems as
>
> though the timeout for AX routines has increased from the 3 seconds in
>
> Jaguar to about 6 seconds in Panther.
>
>
>
> Is this correct, and if so, why was this done?
>
>
This was caused by a change lower in the system. And yes is about 6 second
>
timeout.
>
Shame :(
>
>
>
> Would it be worth me adding a feature request to Radar asking for the
>
> timeout value to be settable by the calling app?
>
>
Nope. We already have a radar for that :-)
I might still add one anyway so I get notified if it ever gets done.
>
> Is there anyway to tell that the app being observed is not currently
>
> responsive without having to try using AX (and waiting for the timeout)?
>
>
There is no published way of doing this. Threading your calls to
>
accessibility on an app by app basis is probably the best workaround.
>
I thought as much, but its not going to help much as this is being done just
before bringing up a menu with the app's windows in it, so I would have to
wait for the thread to finish before showing the menu anyway.
Matt
_______________________________________________
accessibility-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/accessibility-dev
Do not post admin requests to the list. They will be ignored.