You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
While experimenting with the OSC client ( in C) , I noticed that the button messages are send after the event happened : if you press a button more than 2 sec.. then you receive the message "long pressed"... but after 2 seconds and the message is sent once the button is released.
Not really good at programming in C, I do not really understand how I could modify the main.c for doing the following:
Once user presses the button, the OSC routine immediately sends "button_is_being_pressed" and once the button is released sends "button_ released". In other word, to send the real status of the button.
This would help tremendously in combining Pots and Button in the following way:
Pot and No but -> do something
Pot + Button_being_pressed_while_turning_pot -> do something else
Hoping that someone could help,
Thank you a lot
The text was updated successfully, but these errors were encountered:
Hello,
While experimenting with the OSC client ( in C) , I noticed that the button messages are send after the event happened : if you press a button more than 2 sec.. then you receive the message "long pressed"... but after 2 seconds and the message is sent once the button is released.
Not really good at programming in C, I do not really understand how I could modify the main.c for doing the following:
Once user presses the button, the OSC routine immediately sends "button_is_being_pressed" and once the button is released sends "button_ released". In other word, to send the real status of the button.
This would help tremendously in combining Pots and Button in the following way:
Pot and No but -> do something
Pot + Button_being_pressed_while_turning_pot -> do something else
Hoping that someone could help,
Thank you a lot
The text was updated successfully, but these errors were encountered: