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
Dropping the diagram in here from #54 (comment) of how an event could bridge the gap between keys and LEDs so that the keyboard server doesn't have to know about LEDs and the animation engine doesn't have to know about keys. This would also allow the application to send events to the engine, allowing for software-based events.
Will Event be capable of handling key hold and key up. These other event types might be useful in much more complex animations such as intensified ripples, where a ripple can increase intensity the more the key is held.
Will Event be capable of handling key hold and key up.
That's a really interesting idea. If we sent an %Event{}, we could have a :type property that could hold that sort of information. Also to decouple events from the concept of keys, we could support "momentary" and "latching" events, which could have types like (TBD) momentary, on, and off. This could represent key press, key up, key down, as well as a variety of other things with similar behavior.
May overlap with: #43
See comment: #54 (comment)
There was another comment somewhere about not coupling Keys to LEDs and looking up by coords to feed the event to interact. Can't find the comment.
There's also this comment, which might be more about layouts than about interactions, but I feel this is all tied together: #54 (comment)
The text was updated successfully, but these errors were encountered: