Lumino
#87
Replies: 1 comment
-
|
Figured out how to get lumino to properly respond to pointing device behavior. Mostly, it's pullling the "default" case from process_record_lumino. It might be worth pulling that code out to a function (as well as the event count part) into separate function(s), to be more easily triggered. |
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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
First, I want to say that the Lumino module is awesome, and nice.
However, I have noticed a couple of things:
Because of a deviation between the normal formatting of function calls, a couple of the module functions don't call the sub-functions. (I have a PR for this already: getreuer/qmk-modules#6).
Not a huge issue, since the issue I ran into with it can be worked around easily enough. (namely, I have a hacky config for rgblight to dump it's info into rgb matrix for multiple animations, and need to sync the value settings)
Also, instead of using
QK_BOOTto add the shutdown/boot led, there is theshutdown_(module)hook.Additionally, using the timeout option, it doesn't trigger the timer reset on encoder events nor does it trigger on pointing device movement. This is because it's using
process_record_*function to reset the timer. However, it might be better to uselast_input_activity_timeorlast_input_activity_elapsed, as these are reset on any activity (matrix, encoder, and pointing) and can provide a much more unified experience.Beta Was this translation helpful? Give feedback.
All reactions