Problem is that Buttons first sends a true and then on mouse-up it sends a false. It’s a bug, and it’s usually not visible, unless you drive some code which then runs twice.
If the Button would send a “1” on press and “-1” on release, and of course “0” in resting position, the problem could be solved more easily on the receiving end. Now I have to toggle states inside components which makes the logic look weird.
I often use RCP and often not. In most cases also RCP must work for a boolean control…
And yes, the Value List can solve the dblclick Toggle Button problem as long as it is used only on the GH canvas.
Boolean Toggle is also an okay workaround (and actually is single-click in the RCP, acting like a radio-button!). I tend to use these in cases where a Button might freeze the canvas, or, simply hold Button down while clicking until the process it activates is done computing (which appears not to freeze the canvas).
Hi. I was struggling to find a solution. But here it is. Workaround, but … sends “true” only once when clicked. You just have to set “record limit” for the “data recorder” component to “1”.
EDIT: Altgough the panel truly shows just one value per click, the rest (when something connected to the panel) somehow behaves as before I am sad.