If you get it latching, change the upclick vote to a higher priority, or the downclick vote to a lower priority. Only time it latches is when you click faster than the sample rate of the gui portion of the program. This is settable in the timer area. Faster the frequency, the faster you have to click to vote 2 times down in the same period, or down and up in the same period. Also faster the frequency CPU cycles goes up obviously.
As to changing a button from toggle to momentary on the fly, I have not thought about that. I am sure it can be done with some fancy logic where the button changes a variable, and the uplick changes a variable, and depending on another variable that determined momentary/toggle the button's variable would either increase or not making an output on or not. I would have to think about it more though.
Have 1 logic section that says if (DigitalOutput0 && DigitalOutput1) connected to an output. Then in the then do area put the then statement to be turn on DigitalOutput3, and in the anti-then statement put in turn off DigitalOutput3. Done.
It forces a boolean operation because each output is an if/then/else. If(42) doesnt makes sense, but if(true) does, and boolean gives a true/false, where non-boolean doesnt.
If that doesnt make sense I can give some more input. Let me know.