tib

Well I think it is not practical to reconfigure the drivers every time the user changes the layer or presses a modifier key. The sensors should just report raw movements,...

I have been inspired by this video: https://www.youtube.com/watch?v=FSy9G6bNuKA please take a look, and you will understand, why the resolution is important for me. :) I haven't studied much the source...

> > If so, the states sharing mechanism between processor should be considered🤔 > > Definitely! > > I'm considering to use `&RefCell` to share the states across the processors,...

This is definitly not good: ``` hrm_keys = "a s" ``` If you switch default layers between Qwerty, Colemac or Dvorak, such configuration makes no sense, that is why i...

How is this issue is different from https://github.com/HaoboGu/rmk/issues/231 ? Anyway, see https://github.com/HaoboGu/rmk/issues/268#issuecomment-2701991941 as an idea.

Can you show a preview, how the config file will look like?

Nice! And do you want to edit these macros later with Vial? Or is it possible at all to use Vial for this if you have so many of them?...

Is there a plan to support "NKRO"? Because that (if I know right) NKRO also needs the state storage of every keys, not only 6 + modifiers. But of course...

Just do not predefine these aliases in RMK, because Swedish, Danish, German, Hungarian, etc. layouts may all have different position of the "same" letter! And also the symbols which are...

if you would use config file there this is possible: [aliases] "~"="WM(Grave, LShift)" "!"="WM(Kc1, LShift)" "@"="WM(Kc2, LShift)" "#"="WM(Kc3, LShift)" "$"="WM(Kc4, LShift)" "%"="WM(Kc5, LShift)" "^"="WM(Kc6, LShift)" "&"="WM(Kc7, LShift)" "*"="WM(Kc8, LShift)" "("="WM(Kc9,...