Re: AX[Visible]Columns and a custom control
Re: AX[Visible]Columns and a custom control
- Subject: Re: AX[Visible]Columns and a custom control
- From: Ricky Sharp <email@hidden>
- Date: Sun, 3 Sep 2006 22:04:40 -0500
On Aug 28, 2006, at 7:19 PM, Ricky Sharp wrote:
On Aug 28, 2006, at 5:09 PM, Mike Engber wrote:
Seems like it might be better (and more simply) represented as an
AXList.
There appears to be a serious problem with AXList. When I return
that as a role, the VoiceOver cursor never moves to that control.
They keyboard focus does, as I see my custom focus ring. I have my
Acc settings to have the VO cursor follow the keyboard cursor.
VoiceOver also doesn't speak anything when I move the mouse over my
control.
Going through System Prefs, I can only find one control that is an
AXList; the list of accounts in the Accounts pane. The VoiceOver
cursor doesn't move either to the list even though the keyboard
focus does. The VO cursor remains on the control that it was on
prior to tabbing (or shift-tabbing) to the list. VO also doesn't
speak anything when over the list.
Simply having my control use a role of AXTable eliminates the
problem. Also, all controls in System Prefs that use AXTable work
a-ok with VO.
I'm running Mac OS X 10.4.7 on PPC (dual G5).
If this isn't a bug that's already filed, I'll file one.
So, I will still need to provide a solution and it appears I need
to stick with AXTable. I agree though that, had it worked, AXList
would have been a simpler implementation.
I completely re-implemented my control as an NSMatrix subclass
(IIList) containing NSActionCell (IIListCell) cells. I'm now not
implementing any custom accessibility code. IIList automatically
picks up a role of AXList and my cells pick up AXStaticText. This is
a simple list where I basically just needed a single column that will
display names of people. It's also a single-select list, so it acts
just like a set of radio buttons.
Also, I do not have any of the problems as I wrote above. The
VoiceOver cursor can move to both the scroll area (my IIList lives
inside an NSScrollView) as well as to the individual cells.
It thus appears that there are no bugs with AXList. Perhaps the
Accounts pane list needs to have its cells modified to accept the
first responder?
___________________________________________________________
Ricky A. Sharp mailto:email@hidden
Instant Interactive(tm) http://www.instantinteractive.com
_______________________________________________
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