Awesome, thanks!
I don’t see a logical reason to need/use the pre/postfix with buttons. With only two discrete values from a button (on|off), I don’t really see much of a need access to the value surrounded by message data…
However, the idea about different popuptext messages for on|off states, I could easily see some use out of that. For example, imagine a button that makes a new plant visible with a bunch of widgets.
Instead of the popuptext message being: “Display FX Window: 0” and “Display FX Window: 1”, it could be “Display FX Window” and “Hide FX Window”.
I know this seems like it could just be the button text, but in a cramped and busy plant, it would help minimize the need for lengthy detailed explanations on the buttons themselves.
Speaking of, this was also the reason I had asked about newlines in popuptext way back way back: https://forum-next.cabbageaudio.com/t/are-newlines-in-popuptext-popup-pre-post-fix-possible/1506
I’m still interested in both the ability to use newlines in cabbage sections (basically, would a simple expand of \n work?), AND if used with chnset having it incorporate pre/postfix messages. As I explained in the other thread, I try to avoid using chnset for the messages if at all possible to keep some semblance of simplicity, but I would still consider losing the pre/postfix when using chnset a bug.