emulation or support for both "release_msg" and "press_msg" for buttons

[newville]

When auto-translated ADL screens, we have noticed that Buttons that use both "press" and "release" messages have only the "press" message translated to BOB screens. There is a warning for this, which is helpful.

Can this be supported in the ADL-to-BOB translator? If not, is there a suggestion for how to emulate this in CS Display Studio? It looks like an Action Button can write to a PV, but I don't see an obvious way to distinguish between "button press" and "button release". Or is the recommendation to have a script that does something like

       execute_press_action()
       sleep for a millisecond
       execute_release_action()

?

[georgweiss]

The ActionButton only handles button press. There is no handler for the MOUSE_RELEASED event.

In the case of a "write PV action", what should a execute_release_action do?

[kasemir]

This was a speciality of MEDM: Pressing the button could write 47, releasing the button could write 192. You can configure completely random values.
Pretty much all the other display tools support buttons that write 1/0 or true/false. In the display builder, we do that with the boolean buttons. We also support writing any configurable value on press, but then nothing on release, with the action button.
In the specific case, I'd check if maybe a boolean button that writes 1/0 will do what's needed. If you really need to write two different values, then that has to be done by putting a calcout into the IOC.

[newville]

@kasemir

This was a speciality of MEDM: Pressing the button could write 47, releasing the button could write 192. You can configure completely random values.
Pretty much all the other display tools support buttons that write 1/0 or true/false.

Well, caQtDM also supports both putting any value on "press" and separate "pressMessage" and "releaseMessage" for arbitrary values, with "pressMessage" setting a value to some string/float, and "releaseMessage" setting a different value.

Converting to BooleanButton might help with many of the cases we have.