Re: Problem with kEventMouseDown
Re: Problem with kEventMouseDown
- Subject: Re: Problem with kEventMouseDown
- From: Marc Poirier <email@hidden>
- Date: Mon, 3 Nov 2003 21:35:55 -0600 (CST)
Hmmm, I would have to say that it's really not too hard to catch mouse
events from the root pane control, and if you do that it will be more
correct in this context, and guaranteed to work all of the time (unless
the host is buggy, in which case it's not your fault). I mean, if you
really want to go very low level, I guess you could write something at the
device driver level that is directly dealing with the mouse hardware, but
I can't imagine that that will be easier than just installing a click
event handler on the pane control... ;-)
Marc
On Mon, 3 Nov 2003, [ISO-8859-1] Hans Mvller wrote:
>
Thanks for the help, but I wont work so easily for me because I am
>
using a cross-platform framework that using its own event handling. I
>
need to catch the mouse events at a very low level to make it work. It
>
makes it really hard to use kEventClassControl events on the panel
>
because the plugin uses its own event handling(not carbon events).
>
>
Do you know any other solutions to get the low level mouse events.
>
>
Regards
>
Hans Mvller
>
>
svndagen den 26 oktober 2003 kl 20.56 skrev Marc Poirier:
>
>
> You are probably better off grabbing control class mouse events in your
>
> root pane control or sub-controls. You should avoid installing window
>
> class event handlers since the window belongs to the host and the host
>
> may
>
> have other expectations, and moreover, the host may install a window
>
> event
>
> handler on top of yours, which could cause the problems that you are
>
> experiencing. The root pane control that you create belongs to you,
>
> but
>
> not the window. The control class mouse events that I'm talking about
>
> are
>
> kEventControlTrack, kEventControlClick, and
>
> kEventControlContextualMenuClick (which each have different purposes).
>
>
>
> Unfortunately some events can't be gotten from control class and you
>
> need
>
> to use the window event target, but not for what you're talking about.
>
>
>
> Marc
>
>
>
>
>
>
>
> On Thu, 16 Oct 2003, [ISO-8859-1] Hans Mvller wrote:
>
>
>
>> Hello
>
>>
>
>> Im porting a VST plugin using Emagics VST2AU sdk to AudioUnits. My VST
>
>> plugin uses Carbon Events, every thing works except one thing. The
>
>> problem is that my plugin doesn't receive mouse down event
>
>> correctly(kEventMouseDown). The strange thing is that it sometimes
>
>> works, and I dont know when this happens but it's often in combination
>
>> of open closing window, or a debug break point is called, after this
>
>> everything seems to work. So it looks like a timing problem. Other
>
>> events are passed correctly to my plugin(mouse up etc). My plugin
>
>> should receive mouse events first (if I understand the document about
>
>> carbon events correctly) and then passed to the AudioUnit. Does
>
>> anybody
>
>> know what could be the problem.
>
>>
>
>> Regards
>
>> Hans Mvller
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.