I would like to encourage you to skip the fade, and instead use “Set level to” current level -10
My logic is, once a fade starts, it cannot be aborted… Often times, you will want to reduce 20 or 30%, and you will be forced to wait for the first fade to complete before you can drop it another 10%.
Alternatively, if you use the “Set level to” command, you can use the button again immediately ª, if desired.
Just my two cents.
If you think users will press the button (
trigger) multiple times back to back… it is also worth programming this piston to run very swiftly from top to bottom. (which will happen at each press)
Ideally, the piston will be able to run thru the code entirely before the button is pressed again.
ª For clarification,
When I said, “you can use the button again immediately”, that last word, in context, is more like:
(the time it takes for the piston to complete an execution) plus 20ms later
as compared to a fade, which could keep you waiting 10 seconds, or more.