Re: AU automation gestures/scroll wheel events
Re: AU automation gestures/scroll wheel events
- Subject: Re: AU automation gestures/scroll wheel events
- From: Brian Willoughby <email@hidden>
- Date: Mon, 15 Jun 2009 14:32:18 -0700
I think you've misunderstood. There is a difference between a
parameter value change and a gesture. Bill is saying that editing a
text box does cause a parameter value change, and they do set the new
value, but there is no gesture involved.
Unless you have a scroll wheel which can detect when a finger touches
it before a series of changes, and when a finger is removed after a
series of changes, then you do not have a human interface device that
is capable of gestures. Thus, you should not send invented gesture
messages. Just set the new value each time the scroll wheel
changes. That is all.
Brian Willoughby
Sound Consulting
On Jun 15, 2009, at 14:16, Howard Moon wrote:
Ok, but that doesn't answer the question about how to handle scroll
wheel changes that DO cause parameter value changes. Should begin/
end gestures be sent? If so, is there a preferred way to go about it?
On Jun 11, 2009, at 2:47 PM, William Stewart wrote:
we don't send begin/end gestures if the change is not a gesture
that would begin a potential series of parameter changes.
For example, when you directly edit the value of the parameter in
a text box, then we just set the new value - no gesture
Bill
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden