• 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
Accessibility API, thread safe?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Accessibility API, thread safe?

  • Subject: Accessibility API, thread safe?
  • From: George Warner <email@hidden>
  • Date: Tue, 01 Jan 2013 12:28:42 -0800
Can anybody please confirm if it is safe to make multiple concurrent AX calls?
i.e.: calling AXUIElementCopyAttributeValue() from a concurrent queue?

Taking a quick look thru the sources it appears that that API takes locks when it's accessing accessibility objects from the app from which the API was called… and not otherwise (when the targeted app is NOT the app that called the API). This implies two things: 1) local AX accessors are thread save (via the lock) and 2) remote AX accessors are thread save (via serialization forced by the inter app communications).

-- 
Enjoy,
George Warner
Schizophrenic Optimization Scientist
Apple Developer Technical Support (DTS)
eMail: <email@hidden>
iChat: <email@hidden> 

 _______________________________________________
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
  • Prev by Date: Re: Accessibility API, thread safe?
  • Next by Date: Voice over selecting hidden items
  • Previous by thread: Re: Accessibility API, thread safe?
  • Next by thread: Voice over selecting hidden items
  • Index(es):
    • Date
    • Thread