Open ndonald2 opened 11 years ago
Sounds good. I like the clarity of the name ControlTrigger, and the trigger method, but see that's it's totally redundant. I'd be ok with just removing it if you felt that's the way to go, but I'm inclined to keep the class, just turn it in to a wrapper as you suggest.
I think keeping it as a wrapper definitely has value, and having it output a float value of 0 or 1 depending on the triggered state may prove useful.
I just noticed this. The only difference is the interface - both will output a particular value with a "triggered" status when you either call
setValue()
ortrigger()
.ControlValue
also responds toforceNewOutput
but I want to phase that out when I refactor the synthesis context stuff.Maybe
ControlTrigger
just wrapsControlValue_
but the output value is limited to 1 when it's triggered and 0 when it's not?