From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
09-25-2006 10:00 AM
09-25-2006 10:05 AM
09-25-2006 10:09 AM
09-25-2006 10:36 AM
Hello,
Thanks for the quick response. I have never used an event structure, do you have examples of using a event structure for a knob?
09-25-2006 10:46 AM
09-26-2006 02:46 AM
01-16-2007 03:58 PM
01-18-2007 04:02 PM
01-18-2007 04:09 PM
I'd just like to suggest that you attempt to use only the Value Change event on your knob. Things are usually much simpler if you can avoid having to look at mouse down / mouse up, and it sounds like Value Change is exactly what you want.
Also, to avoid flooding your instrument with commands when the user grabs the knob and drags it around very quickly, you might consider setting the increment value of the knob to a reasonable value for your application, so that every pixel of mouse movement while they've grabbed the knob doesn't cause its value to change.
Good luck!
01-18-2007 05:32 PM
@Jeff B wrote:
Also, to avoid flooding your instrument with commands when the user grabs the knob and drags it around very quickly, you might consider setting the increment value of the knob to a reasonable value for your application, so that every pixel of mouse movement while they've grabbed the knob doesn't cause its value to change.
... Or simply flush stale events by comparing the event value terminal with the actual knob value, then skip computations unless the two values are equal.
See the "selective update" example here: http://forums.ni.com/ni/board/message?board.id=170&message.id=207811#M207811