• 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: AXObserverRemoveNotification & destroyed elements.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AXObserverRemoveNotification & destroyed elements.


  • Subject: Re: AXObserverRemoveNotification & destroyed elements.
  • From: Mike Engber <email@hidden>
  • Date: Fri, 2 Jun 2006 16:54:58 -0700

On Jun 1, 2006, at 3:45 PM, Tom Bunch wrote:
Are our observers automatically unregistered for notifications regarding destroyed AXUIElements? If I call AXObserverRemoveNotification with a destroyed element I get kAXErrorInvalidUIElement.

Once a ui element is destroyed, you don't have to worry about unregistering for it.


-ME

_______________________________________________
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


References: 
 >AXObserverRemoveNotification & destroyed elements. (From: Tom Bunch <email@hidden>)

  • Prev by Date: Re: Where does the accessibility hierarchy "start"?
  • Next by Date: NSStatusItem doesn't send kAXMenuOpenedNotification when it pops up menu?
  • Previous by thread: Re: AXObserverRemoveNotification & destroyed elements.
  • Next by thread: Comparing AXUIElementRefs? AXUIElementCopyElementAtPosition(systemWide)
  • Index(es):
    • Date
    • Thread