Thanks Curt, of course I tried that. it is hard to tell when exactly nspopover
creates and manipulates its opaque window.
The real problem is, this call can only (hopefully) set the first responder of
the popover. It can't make the whole popover active. For that you'd need
something like make
On May 10, 2012, at 2:06 AM, Motti Shneor wrote:
> does anybody know how to regain focus on an NSPopover after it lost user
> focus? (after another window becomes key and main) I could not do it. The
> only way I found was to close/delete the NSPopover and recreate it. Seems bad
> solution to m
Thanks, but the accessibility-dev is by itself arcane, to say nothing of
Accessibility engineers.. :)
I've been trying to get useful info there for many issues I had in the past, to
no avail. I was hoping to have at least the non-accessibility issues helped
here.
does anybody know how to regai
On May 9, 2012, at 5:16 AM, Motti Shneor wrote:
> 3. As NSPopover manages its internal window in a very-opaque way, I can't
> find a way THAT WORKS to set up the "initialFirstResponder", or window title,
> or any accessibility attributes on the popover window.
Can you override -viewDidMoveToWi
On 9 May 2012, at 7:16 AM, Motti Shneor wrote:
> I am experiencing grave problems setting up decent accessibility on my
> NSPopover. Most issues affect VoiceOver users, but some affect all users (not
> even accessibility).
Accessibility can be arcane (and buggy). Your best bet is the accessibi
Hi everyone.
I am experiencing grave problems setting up decent accessibility on my
NSPopover. Most issues affect VoiceOver users, but some affect all users (not
even accessibility).
1. When NSPopover is shown, VoiceOver will only report the CONTENTS of the
popover (it will say: "3 items" nev
