• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: AU automation gestures/scroll wheel events
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AU automation gestures/scroll wheel events


  • Subject: Re: AU automation gestures/scroll wheel events
  • From: Howard Moon <email@hidden>
  • Date: Tue, 16 Jun 2009 07:15:51 -0700

I understand fine, but the question was asked and never directly answered. Describing how an edit box works does not address the fact that users might expect automation to work the same when using a scroll wheel to turn a knob as they would with the mouse itself moving the knob. (As witnessed by the original question and at least one responder.) Obviously there may be no mouse down/up to detect, and that led to the issue of whether and how to inject a gesture that would handle it. I was just trying to get an "official" opinion on that concept. Management decisions & requests are often driven by user demand, not by logic, and it's always better to have the proper ammunition when fighting back. Just trying to load up. :-)

Thanks,
	-Howard

On Jun 15, 2009, at 2:32 PM, Brian Willoughby wrote:

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
  • Follow-Ups:
    • Re: AU automation gestures/scroll wheel events
      • From: Stephen Blinkhorn <email@hidden>
References: 
 >Re: AU automation gestures/scroll wheel events (From: Jim Wintermyre <email@hidden>)
 >Re: AU automation gestures/scroll wheel events (From: Brian Willoughby <email@hidden>)
 >Re: AU automation gestures/scroll wheel events (From: William Stewart <email@hidden>)
 >Re: AU automation gestures/scroll wheel events (From: Howard Moon <email@hidden>)
 >Re: AU automation gestures/scroll wheel events (From: Brian Willoughby <email@hidden>)

  • Prev by Date: MIDIGetNumberOfSources not enumerating virtual midi devices (?)
  • Next by Date: Re: MIDIGetNumberOfSources not enumerating virtual midi devices (?)
  • Previous by thread: Re: AU automation gestures/scroll wheel events
  • Next by thread: Re: AU automation gestures/scroll wheel events
  • Index(es):
    • Date
    • Thread