(I know: I'm making my own life difficult... but...)
I have a couple of projects - one of which I have already put up here - which are subflows to give you a safety feature that you have to double click a button before it toggles.
So Today's question is about how that should work.
Reason: I am wanting to make a similar subflow that doesn't have the TOGGLE feature.
But to get the button pressed, you still have to double press the button.
1 - I'm torn between making another subflow as opposed to adding to the existing one and adding the option so there is no toggle feature.
2 - Is this worth the effort? Though if you have protection on toggle buttons, you will need/want it on single press buttons. So there isn't much love lost on having a slightly bigger subflow than having TWO that do slightly different things.
With things as they are - on the existing subflow:
As you press the button, the output changes IN TIME with the buttons being pressed.
Then it re-asserts the final selection when you stop pressing the button.
Ok, it doesn't do that. Sorry.
Is this good/bad? -- semi rhetorical, as I can see reasons for doing this and problems if I don't. Although that is only one side of it, I feel it is probably better doing it this way.
So, the extra work needed to modify the existing code to make it Double click to activate has it's own set of questions:
You must double click to get the output to change.
So what happens to the output if you quickly press the button THREE times?
Should the output then STAY at that signal or should it send a pulse message starting with ....
0. Send a
1 if/when the button is DOUBLE clicked then go back to the
Or - only to make it more complicated:
I am going batty thinking about what is the right way
Thanks in advance.