Thank you very much for taking the time to build a test and make a reply.
I don't (in general) actually have custom subviews. The clicks were tested
(among other places) in parts of the NSWindow to which I have not
explicitly added content, as well as standard classes like NSBox. I was
suggesting
> On Oct 20, 2019, at 8:27 AM, Aandi Inston wrote:
>
> We have a workaround, which is to move our right click processing onto
> MouseUp, which is passed up the responder chain as we wish in both 32 and 64
> bit systems. But I remain curious as to what the docs are actually telling me.
From
" Why are you compiling a plugin for 32 bits?" Because plug-ins must match
the host app. In this case the host app's 64 bit version was only released
4 years ago. (The host app is made by a third party).
Older versions of the app run on 10.14 and are still widely used by our
customers. So, while
Your email client line breaking makes for very difficult reading so I
reformatted. See below.
Why are you compiling a plugin for 32 bits?
Just tested a 64 bit app linked to 10.8 and an unhandled rightMouseDown is
passed promptly from view to window. Testing in 32 bits would be a lot of work.
I believe I may be seeing an effect described in the Cocoa docs for the
rightMouseDown:
method. I am unsure exactly what the docs are saying however. Symptom:
compiled for
64-bits, an unhandled rightMouseDown: is eventually sent to the NSWindow
subclass,
but compiled for 32-bits (and run on
