kiibohd
Configurator doesn't assign None to cleared keys
If a key is left as the default on the configurator, the resulting kll file will have something like U"5" : U"5";, as expected. But if the key is cleared on the base layer, it won't be put in the generated kll file at all, so it will fall back to the default defined in the scan map rather than doing nothing.
Oh, just saw the "None" button, although it might still be confusing to visually have nothing on the key in the configurator, but still have the key do something when pressed.
Yeah, I have to make the distinction between Clear and None. I am open to labels that are more clear however (None is the keyword used in kll).
On Tue, Apr 26, 2016 at 9:53 AM Matt Ventura [email protected] wrote:
Oh, just saw the "None" button, although it might still be confusing to visually have nothing on the key in the configurator, but still have the key do something when pressed.
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/kiibohd/KiiConf/issues/34#issuecomment-214809337
Something like "No action" might be more clear. But on the base layer specifically, some possible ideas would be:
- Only have a None option
- Cleared keys will default to None when generating the kll
- Clear is replaced with a reset to default button which will restore the default mapping, None works normally.