> On 12 Mar 2015, at 16:17, Uli Kusterer wrote:
>
> On 12 Mar 2015, at 01:09, Mutlu Qwerty wrote:
>> self.nextResponder = super.nextResponder //insert self into the
>> Responder chain
>
> I think you mis-typed here. super nextResponder calls the superclass's
> implementation of -nextR
On 12 Mar 2015, at 01:09, Mutlu Qwerty wrote:
>self.nextResponder = super.nextResponder //insert self into the
> Responder chain
I think you mis-typed here. super nextResponder calls the superclass's
implementation of -nextResponder, but it still just calls nextResponder with
self be
I thought Yosemite view controllers put themselves in the responder chain
properly now...
Sent from my iPhone
> On 2015/03/12, at 9:20, Jens Alfke wrote:
>
>
>> On Mar 11, 2015, at 5:09 PM, Mutlu Qwerty wrote:
>>
>> self.nextResponder = super.nextResponder //insert self into the
>>
> On Mar 11, 2015, at 5:09 PM, Mutlu Qwerty wrote:
>
>self.nextResponder = super.nextResponder //insert self into the
> Responder chain
That just sets the object's nextResponder property; it doesn’t insert the
object into the responder chain. I think you want to set the _view’s_
nex
