On Oct 29, 2014, at 12:17:58, Jonathan Mitchell <jonat...@mugginsoft.com> wrote:
> Sure. This is expected behaviour for NSButton subclasses of NSView. > > The docs for NSView acceptsFirstMouse: state: > > Override this method in a subclass to allow instances to respond to > click-through. This allows the user to click on a view in an inactive window, > activating the view with one click, instead of clicking first to make the > window active and then clicking the view. Most view objects refuse a > click-through attempt, so the event simply activates the window. Many control > objects, however, such as instances of NSButton and NSSlider, do accept them, > so the user can immediately manipulate the control without having to release > the mouse button. I know. As I said in my first message, I'm trying to *prevent* this behavior on the entire window for all subviews withOUT having to subclass every conceivable class that I might add to my window. -- Steve Mills Drummer, Mac geek _______________________________________________ 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
