On Wed, Oct 29, 2014, at 11:46 AM, Steve Mills wrote: > 3. It can be dangerous if you forget that an app exhibits this behavior > and you accidentally click a control in the background when you simple > wanted to activate the window, and that control deletes something, > changes something, or otherwise messes stuff up.
This is what I remember the guideline to be, and I believe it's why Safari prevents any clicks on background windows from going through to the WebView. (Safari doesn't know what clicks are "innocuous".) You can always click the close button on a window without bringing it to the foreground, though. And you can hold down the Command key to send a click to a background window without bringing it to the foreground (though I haven't tested whether this overrides the window's desire to avoid destructive background clicks). Steve, you might have to subclass NSWindow and override -sendEvent:. May I suggest you let background window clicks go through to certain key buttons, like "mute playback"? --Kyle Sluder _______________________________________________ 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
