Sent from my iPad
On May 21, 2013, at 1:32 PM, Steve Mills <smi...@makemusic.com> wrote: > On May 21, 2013, at 12:06:15, Kyle Sluder <k...@ksluder.com> wrote: > >> One concern is that you're not going to get a mouse event for clicks that >> happen in other apps' windows, but that might actually be what you want. > > Good point. No, this window should behave like it's really is a popup in the > sense that *any* click outside it will dismiss it, and if those clicks are in > other apps, the window will dismiss and the click will go through to the > other app. > >> An alternative approach would be to put up a transparent shielding window >> underneath your browser, and have any clicks on it dismiss the browser. > > Hmm. But if the shielding window gets the click to dismiss the popup window, > then the click won't go through to other apps, so it wouldn't have that > "clicking outside the popup on another app dismisses the popup and switches > to that app" behavior. Is it safe to create a new mouseDown event for the > clicked point, but without the window filled in, and post it to the OS so it > goes through to the other app? This is an area I've never dabbled in before. > (Heck, this whole thing is on my undabbled list.:) > Hi Steve. Reading your issue sparked a flashback to the mid '90s where we had the same issue in Director products. Not sure if this is able to be handled the same way but we would create a shielding rect to catch the click behind our popup style graphic and if it registered, issue a dismiss to the graphic and a "pass" that allowed the event to continue propagating. One other option may be to catch the click at location, dismiss your GUI element and rebroadcast the event so that it could be recaught by whatever is in scope. Of course, you would need to have the proper context to issue the event to if you went that route. Just a thought/2. > -- > Steve Mills > office: 952-818-3871 > home: 952-401-6255 > cell: 612-803-6157 > > > > _______________________________________________ > > 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/zav%40mac.com > > This email sent to z...@mac.com _______________________________________________ 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
