• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSView nextResponder always the viewController?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSView nextResponder always the viewController?


  • Subject: Re: NSView nextResponder always the viewController?
  • From: Lee Ann Rucker <email@hidden>
  • Date: Wed, 17 Dec 2014 01:19:32 +0000
  • Thread-topic: NSView nextResponder always the viewController?

I don't know the answer to that, but even before 10.10 I had problems with inserting responders and found that 10.7's supplementalTargetForAction:sender: did everything I needed insertion for. If that works for what you need it's so much easier to manage.


On Dec 16, 2014, at 3:51 PM, Gordon Apple <email@hidden> wrote:

> In Yosemite, any included viewController is automatically inserted into the
> view¹s responder chain. Something is not working right. In many of our
> views, we insert controllers (derived from NSResponder) A and B into the
> view¹s responder chain. A must come first, then B, so B is inserted first as
> the view¹s next responder, then A. The expected (and previous) result is
> view -> A -> B -> viewController -> whatever. However, after each insertion
> of A or B, the view¹s next responder is still the viewController. In fact,
> what we get is view -> viewController -> A -> viewController -> A -> ...  ,
> a nice little infinite loop. What gives here? Is the view¹s viewController
> now somehow hard-wired such that it is always the view¹s next responder, and
> we can¹t change it, and can only append after the viewController?
>
> When I first heard about this new feature, I thought it was a good idea.
> Now, I¹m not so sure. Another issue we have always had to deal with in the
> view is that drag/drop are not standard events and have to forwarded to a
> delegate if you want to handle them elsewhere.
>
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.apple.com_mailman_options_cocoa-2Ddev_lrucker-2540vmware.com&d=AAIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=ie7S-J__EKnfyVOBV7-jV2rZ--p47O6vkyTklpDM3h4&m=ypgtZPUqtywUVVZHYVpvRC6uUXwGKX7DPHcDk8bkEhA&s=wusgKJ2hoyOyJ4p70vDSgSAFP5hFwIkmTysNxFmLS0c&e=
>
> This email sent to email@hidden


_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >NSView nextResponder always the viewController? (From: Gordon Apple <email@hidden>)

  • Prev by Date: NSView nextResponder always the viewController?
  • Next by Date: Re: Issues with applications running on background (Alarm Application)
  • Previous by thread: NSView nextResponder always the viewController?
  • Next by thread: Re: NSView nextResponder always the viewController?
  • Index(es):
    • Date
    • Thread