Re: Where to catch notifications when inspecting a Carbon application?
Re: Where to catch notifications when inspecting a Carbon application?
- Subject: Re: Where to catch notifications when inspecting a Carbon application?
- From: Bill Cheeseman <email@hidden>
- Date: Fri, 01 Jun 2007 16:18:52 -0400
- Thread-topic: Where to catch notifications when inspecting a Carbon application?
on 2007-06-01 2:44 PM, David Niemeijer at email@hidden wrote:
> I now confirmed the same issue on TexEdit Plus versus TextEdit using
> UI Browser to watch for notifications. Begins to look more and more
> like a bug to me rather than my error.
Bear in mind that UI Browser does work around some bugs in the accessibility
API, so the fact that something works in UI Browser does not always mean
there is not a bug in the accessibility API. But in Tiger there are only a
couple of bugs left that I have to work around, so in most cases if it works
in UI Browser it should also work in any application that uses the
accessibility API correctly.
By the same token, of course, I'm sure there are still some bugs in UI
Browser, so a failure in UI Browser does not necessarily prove a bug in the
accessibility API.
But I had not been aware of the issue you're tracking down, so UI Browser
uses plain-vanilla accessibility code for this case. If it doesn't work in
UI Browser, there probably is a bug in the accessibility API as implemented
in the target application.
When testing notifications, be aware that UI Browser makes its best guess as
to which notifications a particular kind of UI Element supports. So the fact
that you don't see a particular notification listed in UI Browser's
notifications drawer when a particular UI element is selected does not
necessarily mean that that UI element doesn't support the notification.
There is a new preference in UI Browser 2 that lets you list all
notifications for all UI elements, and this feature was designed for exactly
what you're doing: trying to track down whether a particular UI element
actually supports a particular notification.
It can also be very useful to select the root application UI element in UI
Browser, then register to observe the notification you're investigating.
When the notification is triggered by any UI element in the target
application, you can see which UI element triggered it in the notification
observer window -- and double-click it in that window to automatically
select it in the main browser view.
Bill
_______________________________________________
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