Provide easy-to-use configuration for input devices in `keyboard.toml`

[HaoboGu]

[tib888]

See also #268 (comment) as an idea.

[adong660]

@HaoboGu

Hi. I notice that the docs documented on how to configure actions of rotary encoders by writing some encoder_map = .... But if I'm not mistaken, the current implementation sets all of them to k!(No) in the expanded function get_default_encoder_map. Are we going to implement it or seeking a more general way to configure encoders first?

[HaoboGu]

Hi. I notice that the docs documented on how to configure actions of rotary encoders by writing some encoder_map = .... But if I'm not mistaken, the current implementation sets all of them to k!(No) in the expanded function get_default_encoder_map. Are we going to implement it or seeking a more general way to configure encoders first?

#669 has been merged, so the encoder configuration should work.

Edit: oh that part of doc should not appear in v0.8 doc, it might be a mistake. Anyway, the new version will be released soon

[adong660]

Hi. I notice that the docs documented on how to configure actions of rotary encoders by writing some encoder_map = .... But if I'm not mistaken, the current implementation sets all of them to k!(No) in the expanded function get_default_encoder_map. Are we going to implement it or seeking a more general way to configure encoders first?

#669 has been merged, so the encoder configuration should work.

Edit: oh that part of doc should not appear in v0.8 doc, it might be a mistake. Anyway, the new version will be released soon

Ah, sorry for not seeing that.

[adong660]

Hi. I notice that the docs documented on how to configure actions of rotary encoders by writing some encoder_map = .... But if I'm not mistaken, the current implementation sets all of them to k!(No) in the expanded function get_default_encoder_map. Are we going to implement it or seeking a more general way to configure encoders first?

#669 has been merged, so the encoder configuration should work.

Edit: oh that part of doc should not appear in v0.8 doc, it might be a mistake. Anyway, the new version will be released soon

How about we put encoder_map under [[layers]] rather than under[layout]? Doing so, [layout] would become a description purely for the physical layout, and [[layout]] would handle all the key bindings. (After layout.keymap is completely deprecated.) It'd be clearer to recognize which encoder action corresponds to which layer, and be also easier for users to change the order of layers. An example would be:

[layout]
rows = 5
cols = 4
layers = 3
matrix_map = """
(0,0) (0,1)
"""

[[layers]]
name = "base_layer"
keys = """
A B
"""
encoders = [["C", "D"], ["E", "F"]]

[[layers]]
name = "number_layer"
keys = "..."
encoders = [["1", "2"], ["3", "4"]]