On Mar 27, 2007, at 9:57 AM, Chinh Nguyen wrote: I've got a floating compositing window I load from a NIB populated with a bunch of bevel buttons, a static text field, and a separator. For contextual menu support, I installed a kEventControlContextualMenuClick handler to the content view. When I right click on the window, if my click lands on the static text control, separator, or window, my contextual menu appears in the correct place. But if I right click on a bevel button, my contextual menu appears in the wrong place. After some debugging, it appears that even though I installed my contextual menu handler on the content view, the kEventParamDirectObject I get back is whatever control I right clicked on. And right clicking on a bevel button returns a point relative to the bevel button, not the content view (even though the other controls are handled properly). Is this normal?
Yes, that's normal. The direct object is placed in the event when it's first sent. The event is sent to whatever view is accepting mouse clicks at that location. If that view doesn't handle the event, then the event propagates up the control hierarchy until it reaches the content view and your handler. There's no opportunity for the direct object to be changed to refer to the current event target, though. The direct object always remains the original view that received the event.
You should probably always get the direct object from the event, get the mouse location, and use HIPointConvert or HIViewConvertPoint to convert the mouse location from the direct object view to your view (or to global coordinates).
-eric
|
