Zack

I'm currently making my first max for live device which has some buttons (live.text objects). I have assigned keybinds to these buttons so that when I press a key, the button will be clicked. The issue is that every time I press a key, the 'toggle state' of the button is switched (toggling the button state between highlighted and not). This causes the buttons to remain highlighted after I press the keybind (you can see in the picture that half of the buttons are highlighted since they were recently pressed).

max for live buttons issue.png

Not only does this look wrong, but it causes some unexpected behavior sometimes (such as causing all highlighted buttons to be clicked automatically if I click the edit device button, for example). I think this functionality comes from the fact that if you use the button with your mouse, then it is only highlighted while the mouse button is held down (and unhighlights when you release the mouse). But the whole point of this device is for me to use keybinds to trigger max for live actions. (Note: all of these live.text objects are in the 'Button' mode).

Any tips for how to solve this, so that they won't get highlighted every time I activate them with a keybind?

Not only does this look wrong, but it causes some unexpected behavior sometimes (such as causing all highlighted buttons to be clicked automatically if I click the edit device button, for example). I think this functionality comes from the fact that if you use the button with your mouse, then it is only highlighted while the mouse button is held down (and unhighlights when you release the mouse). But the whole point of this device is for me to use keybinds to trigger max for live actions. (Note: all of these live.text objects are in the 'Button' mode).

Any tips for how to solve this, so that they won't get highlighted every time I activate them with a keybind?

I'm currently making my first max for live device which has some buttons (live.text objects). I have assigned keybinds to these buttons so t

problem-with-keybinding-buttons-on-device

If anyone ever finds this and needs an answer, I found a hacky solution to solve it for now, from this thread: 

https://cycling74.com/forums/making-live-button-behave-as-momentary/replies/1#reply-5df81a7e0489637bed3203a1

Basically I took the solution from that thread, which immediately unhighlights a button after it is pressed. Then I made a patcher from it, and hooked all of my buttons up to that same patcher on both inlets and outlets. Although if anyone clicks the button and holds it down, releasing the mouse will also cause the button to fire which is unintended (although this doesn't bother me since the whole point of the button is to keybind, so I never use mouseclicks).

unButton-patcher.png

This solution is pretty messy though (needs two connections to every button on the interface), so if anyone knows a better way please let me know.

If anyone ever finds this and needs an answer, I found a hacky solution to solve it for now, from this thread: https://cycling74.com/forums/making-live-button-behave-as-momentary/replies/1#reply-5df81a7e0489637bed3203a1
Basically I took the solution from that thread, which immediately unhighlights a button after it is pressed. Then I made a patcher from it, and hooked all of my buttons up to that same patcher on both inlets and outlets. Although if anyone clicks the button and holds it down, releasing the mouse will also cause the button to fire which is unintended (although this doesn't bother me since the whole point of the button is to keybind, so I never use mouseclicks).
Here is the patcher:


Problem with keybinding buttons on device