Apparently on Leopard (and presumably, early versions of Mac OS X) you
have to handle the mouseDown event in order to receive a mouseUp
event. Initially, I only overrode mouseUp, thinking that I didn't
want to react to the event until the user releases the mouse button
inside the NSRect of
Ok. I went back and did some experimenting and it doesn't look good.
First of all the ignoresMouseEvents property was already set to NO.
Assuming I had some issue with intercepting mouse clicks at the
NSWindow level when an NSView was present, I decided to implement
support for event han
Since the window is transparent and the view is not, maybe the view is
actually getting the mouse event? Maybe. But why does it work on
Snow Leopard? I will test your theory out and get back to you. I'm
not even sure the content-view is a responder but I'll check that out
too.
-Michae
On Sep 12, 2009, at 9:12 PM, Michael A. Crawford wrote:
I have created a borderless window that is used to display a custom
graphic, which need to respond to the enter key or a mouse click by
closing itself. Seems straightforward enough. It works great on
Snow Leopard (10.6) but I do not
I have created a borderless window that is used to display a custom
graphic, which need to respond to the enter key or a mouse click by
closing itself. Seems straightforward enough. It works great on Snow
Leopard (10.6) but I do not get the mouse events on Leopard (10.5).
Hitting the ent
