Continuing the theme of "HS3 is the time for big changes" - I want to gather some quick feedback about buttons.
Buttons, through the above subject script command can be set up to run a script, or they will cause ButtonPress to be called in the plug-in that owns that device.
Do we still need this? Buttons can be added using value/status pairs, and we have added the ability to specify row and column positioning, so eliminating this would result in two changes: 1. No ability to run a script when a button is pressed (other than running it when the value changes to the value associated with that button) and 2. No buttons without values associated with them.
The alternative, if this feature is still heavily used and cannot be replaced with value/status pairs, is to get away from the Chr separated string and go with a structure to be passed instead of a string. The structure would then have a separate field for the script name, and we could even then support a function and parameters, and we could include row and column fields.
My preference is to simplify and get rid of it, but I need to hear if people still use it or plan on using it with HS3 plug-ins.
Thoughts?
Buttons, through the above subject script command can be set up to run a script, or they will cause ButtonPress to be called in the plug-in that owns that device.
Do we still need this? Buttons can be added using value/status pairs, and we have added the ability to specify row and column positioning, so eliminating this would result in two changes: 1. No ability to run a script when a button is pressed (other than running it when the value changes to the value associated with that button) and 2. No buttons without values associated with them.
The alternative, if this feature is still heavily used and cannot be replaced with value/status pairs, is to get away from the Chr separated string and go with a structure to be passed instead of a string. The structure would then have a separate field for the script name, and we could even then support a function and parameters, and we could include row and column fields.
My preference is to simplify and get rid of it, but I need to hear if people still use it or plan on using it with HS3 plug-ins.
Thoughts?
Comment