On Apr 22, 2014, at 6:05 AM, Josh Scotland < email@hidden> wrote:
On Apr 7, 2014, at 4:41 AM, Nick Kocharhook < email@hidden> wrote: So
far so good. But B also slides away after a delay when A is not being hovered by the mouse. Because the buttons inside B are first-level elements, this leads to the absurdity of buttons and text fields showing up in the window’s toolbar. This would not IN
ITSELF be a problem, but that position also affects the order which the items appear in the window. So in some cases, VO will see the close button, the minimize button, one of the header’s buttons, and only THEN the zoom button.
Hey Nick,
I’m still a bit confused by what’s going on and what VO is doing.
It sounds like views are disappearing and VO is building up a weird ordering to navigate the elements. Is that right?
Thanks for the response, Josh. I’ve been away for the last week, but I was glad to come back to this.
The frames of the views are animating to outside of the bounding rect of their superview. The views are thus clipped so they aren’t visible to sighted users. I’m not using -[NSView hidden], and the views are still subviews of the superview. Thus the controls
DO show up to VO users, just in a different location.
I don’t think VO is doing anything wrong here. The goal is to have the controls be in the right place for VO users (w.r.t. stepping through the elements in the window using VO-Right), but still be hidden for sighted users.
One of the options is to turn the alpha off so they’re only visible to VO users and then move them back into place, but that feels quite hacky.
I hope this is enough data to make sense of the request! Please feel free to ask any other questions.
-Nick
|