Re: AXMoved and AXResized notifications don't work?
Re: AXMoved and AXResized notifications don't work?
- Subject: Re: AXMoved and AXResized notifications don't work?
- From: Mike Engber <email@hidden>
- Date: Wed, 24 May 2006 09:07:05 -0700
It was never the intention that AXMoved and AXResized would be
supported by every ui element. It would be very difficult/expensive
to implement. E.g. if a window moves every ui element it contains has
a new position. We would have to send (or at least check for) a
notification on every ui element in the window's hierarchy.
AXMoved and AXResized were conceived of when we were considering
implementing moved and resized notifications for some other ui
elements that weren't windows (e.g. drawers). We didn't want to go
down the route of a AXDrawerMoved, AXFooMoved, AXBarMoved, ...
I would expect that any new ui elements that supported moved or
resized notifications will use AXMoved and AXResized. It would
probably be a good idea for windows to start supporting AXMoved and
AXResized, but they'll still have to continue using AXWindowMoved and
AXWindowResized for backwards compatibility.
-ME
On May 23, 2006, at 5:20 PM, Bill Cheeseman wrote:
I was under the impression that AXMoved and AXResized notifications
(new in
Tiger) could be registered with any UI element and would be
triggered when
that element was moved or resized on the screen. For example, if a
window's
zoom button was registered for AXMoved and the window was moved,
the zoom
button would issue a notification that it has moved.
But it doesn't seem to work.
Are these notifications broken, or do they have some other meaning
and use?
_______________________________________________
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