> On 4 Jul 2016, at 12:00, Charles Srstka wrote:
>
>> On Jul 3, 2016, at 11:35 PM, Gerriet M. Denkmann
>> wrote:
>>
>> When I get an NSStream I do:
>>
>> aStream.delegate = myStreamDelegate;
>> [ aStream scheduleInRunLoop:[NSRunLoop currentRunLoop] forMode:
>> NSDefaultRunLoopMode];
>> [ aS
> On Jul 3, 2016, at 11:35 PM, Gerriet M. Denkmann wrote:
>
> When I get an NSStream I do:
>
> aStream.delegate = myStreamDelegate;
> [ aStream scheduleInRunLoop:[NSRunLoop currentRunLoop] forMode:
> NSDefaultRunLoopMode];
> [ aStream open];
>
> myStreamDelegate then receives stream:handleEven
When I get an NSStream I do:
aStream.delegate = myStreamDelegate;
[ aStream scheduleInRunLoop:[NSRunLoop currentRunLoop] forMode:
NSDefaultRunLoopMode];
[ aStream open];
myStreamDelegate then receives stream:handleEvent: messages.
The documentation says: “The message is sent on the stream objec
Graham,
> On Jul 2, 2016, at 22:45, Graham Cox wrote:
>
> In my app, I ‘m getting this message logged now and again:
I see the same messages from a couple of apps. I enabled the debugging as you
did and investigated to know avail. I chalked it up to some framework code
because all of the st
On Jul 2, 2016, at 23:19 , Jo Meder wrote:
>
> radio buttons which have the same superview and action now all behave as if
> they’re part of one radio group
> Our framework expects the radio buttons to be independent.
> Having AppKit manage them automatically short circuits our UI framework.