Re: Complex controls + TellListener, again
Re: Complex controls + TellListener, again
- Subject: Re: Complex controls + TellListener, again
- From: Urs Heckmann <email@hidden>
- Date: Tue, 8 Jul 2003 15:49:44 +0200
Am Dienstag, 08.07.03, um 15:31 Uhr (Europe/Berlin) schrieb Marc
Poirier:
As a result, I've got two AUCarbonViewControl, so two
MouseDown/MouseUp
messages.
And Logic seems happy about it (but since the MouseDown/MouseUp
messages does not contain the param ID, which I think is a bad thing,
one message should be enough).
No, look again, the AudioUnitCarbonViewEventListener function type
takes
an AudioUnitParameter as one of its arguments, and that struct
contains a
parameter ID value. TellListener is a wrapper for that that takes an
AUVParameter as an argument, which is a class that inherits the
AudioUnitParameter struct, so still, the parameter ID is there.
Hehe, yes, Marc is right 8-)
However, as long as multiple/parallel calls to TellListener do the job
(regardless if from a single CarbonControl or any more complex
approach), I'm happy.
<rule>
Multi-parameter controls send mousedown/mouseup messages for each
parameter they might change during a particular mousing gesture.
</rule>
Can we set that in stone? Bill? Jeff? Everybody?
Thanks,
;) Urs
_______________________________________________
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.