PFUIElementDelegate
IntroductionA formal protocol declaring delegate messages sent by PFUIElement. DiscussionThe PFUIElementDelegate protocol implements two optional delegate methods, PFUIElementWasDestroyed: and PFUIElementReportError:. Clients that implement either of these delegate methods must declare that they adopt this formal protocol. The PFUIElement.h header declares Methods
PFUIElementReportError:Sent when an operation on the receiving UI element generates an accessibility error. - (void)PFUIElementReportError:(NSError *)error; ParametersDiscussionSee -delegate and -setDelegate:. PFUIElementWasDestroyed:Sent when a UI element is destroyed. - (void)PFUIElementWasDestroyed:(NSNotification *)notification; ParametersDiscussionSent from the default notification center immediately after the receiving UI element is destroyed in the running application (for example, when a window closes). The notification parameter is always If this method is implemented in the client, the client is automatically registered for If this element was registered by a client to be observed for accessibility notifications, destruction of this element will automatically unregister it for all registered notifications and update the observers' list of current registrations. This happens after this delegate message is sent and after Some UI elements do not report when their container is destroyed, such as a Cocoa window's title and grow area elements. The -exists method depends on this notification, so it will report that such elements still exist in the running application. See -exists for techniques that can be used to deal with this issue. You can always safely get a destroyed UI element's -pid, and you can always test destroyed PFUIElement objects for equality using A PFApplicationUIElement object never reports when it is destroyed (that is, when the application quits). It does not send this delegate message and it does not post the corresponding notification. See also -delegate and -setDelegate:. |