On 10 Sep 2014, at 23:32, Ken Thomases wrote:
> On Sep 10, 2014, at 4:07 PM, Luc Van Bogaert wrote:
>
>> No succes so far with this.
>>
>> I subclassed NSPanel and overridden:
>>
>> - (BOOL) becomesKeyOnlyIfNeeded
>> {
>> return YES;
>> }
>>
>> - (BOOL) canBecomeKeyWindow
>> {
>> return
On Sep 10, 2014, at 4:07 PM, Luc Van Bogaert wrote:
> No succes so far with this.
>
> I subclassed NSPanel and overridden:
>
> - (BOOL) becomesKeyOnlyIfNeeded
> {
>return YES;
> }
>
> - (BOOL) canBecomeKeyWindow
> {
>return YES;
> }
>
> I also subclassed the collection view in the pan
On 10 Sep 2014, at 01:56, Kyle Sluder wrote:
> On Tue, Sep 9, 2014, at 06:42 PM, Graham Cox wrote:
>>
>> On 10 Sep 2014, at 7:13 am, Luc Van Bogaert
>> wrote:
>>
>>> This opens the panel without making it key, which is OK, but it still makes
>>> the panel key when I click any of the responder
On Tue, Sep 9, 2014, at 06:42 PM, Graham Cox wrote:
>
> On 10 Sep 2014, at 7:13 am, Luc Van Bogaert
> wrote:
>
> > This opens the panel without making it key, which is OK, but it still makes
> > the panel key when I click any of the responder objects in the panel, such
> > as a collectionview.
On 10 Sep 2014, at 7:13 am, Luc Van Bogaert wrote:
> This opens the panel without making it key, which is OK, but it still makes
> the panel key when I click any of the responder objects in the panel, such as
> a collectionview...
'becomesKeyOnlyIfNeeded' does what it says, but how does it de
Hi,
I am implementing some kind of Tools Panel for my document based application
and I'm wondering how one could copy the standard Color Panel behaviour with
respect to its key status.
The Color Panel can be displayed without becoming the key window, it let's the
user use the various controls
