Re: NSAlert

> On Sep 10, 2018, at 12:17 PM, Ben Kennedy wrote: > > Son of a gun. Thanks for elucidating this Richard. Actually Andy Lee was right on when he suggested "it may depend on the setting in System Preferences that governs whether all controls can get keyboard focus". However I could not see

Re: NSAlert

> On 10 Sep 2018, at 11:06 am, Richard Charles wrote: > > On my development machine running 10.12.6 pressing the spacebar will dismiss > a simple NSAlert. This is because in System Preferences > Keyboard > > Shortcuts > Full Keyboard Access > All Controls was selected. (For some > reason it

Re: NSAlert

> On Sep 8, 2018, at 6:25 PM, Andy Lee wrote: > > I don't know where or whether it's documented, but it's not new. > Using Space for "clicking" whichever control has focus has been around > for a while. I don't remember offhand -- it may depend on the setting > in System Preferences that

Re: keyboard focus handling in custom controls

>> On 10 Sep 2018, at 13:21, iain > > wrote: >>> >>> I have an application, which has 3 controls >>> >>> [button] [custom view] [button] >>> >>> I’ve set the NextKeyView of each of them to the control to the right >>> [button] -> [custom view] -> [button] >>>

Re: keyboard focus handling in custom controls

> On 10 Sep 2018, at 2:19 pm, Alastair Houghton > wrote: > > On 10 Sep 2018, at 13:21, iain > wrote: >> >> I have an application, which has 3 controls >> >> [button] [custom view] [button] >> >> I’ve set the NextKeyView of each of them to the control to the

Re: keyboard focus handling in custom controls

On 10 Sep 2018, at 13:21, iain wrote: > > I have an application, which has 3 controls > > [button] [custom view] [button] > > I’ve set the NextKeyView of each of them to the control to the right > [button] -> [custom view] -> [button] > > And the tab and shift tab works between them as

keyboard focus handling in custom controls

Hi, I have an application, which has 3 controls [button] [custom view] [button] I’ve set the NextKeyView of each of them to the control to the right [button] -> [custom view] -> [button] And the tab and shift tab works between them as expected. The situation gets more complicated because the

Re: C++ pointer to Cocoa object

On 8 Sep 2018, at 15:32, Casey McDermott wrote: > >>> If you are using ARC and want to get a strong > reference on the object, you have to use __bridge_retained > > That is handy to know! I see there is also __bridge_transfer to go the other > way. IMO the Core Foundation wrappers