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 (Cocoa-dev@lists.apple.com) 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://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
