Replies: 1 comment
-
The animations for the "real" touch, swipe, long touch and multitouch are in the release, because as you mentioned right, that is the only point, where you can be sure, what event it is. I think you can not take the Color Object to your substitutions, but you can use the color-values (int values for r,g and b) like in the turn_on parts. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Firstly, thats for writing this config. I couldnt have done this without it. This is more of a suggestion and tell me if ive done this wrong "issue" rather than anything wrong with your config
I have noticed that the touch events for a single button are fired before a swipe event causing confusion on use. E.g if i swipe from left to right, the button press animation starts, then the swipe starts.
I have played around with you config and have managed to move the animations from
on_press
intoon_release
.Effectively, on_press does nothing, and actions for
led_on_touch
is moved intohandle_release
. This might not be an issue with the default rainbow config, but I have a custom swipe left/right animation and split a led action between the 3 buttons and they were overlapping.This basically, has the leds above the buttons turn on, but only if a press is detected. A swipe will run the swipe animation instead of running the touch events
Changes made
Remove
on_press
actionAdd swipe animation to
leds_top
:(havnt figured out how to take the variable colors into this lambda)
Added more led partitions for individual top buttons:
add to the top of
handle_release
"then" section:New button scripts:
Beta Was this translation helpful? Give feedback.
All reactions