In KLE you have the option to set a key as a "Decal" which per the KLE hovertext are "Purely Decorative." They even have a button specifically for creating a set of 3 decals for status lights (num, caps, and scroll locks). However when I copy my JSON into the web interface they are mistreated and standard switch holes are cut instead.
The JSON for decals contains the property d:true so a toggle to ignore keys with that attribute would be helpful.
Alternatively, it could be a 3 way toggle since the most common use for decals (that I have seen across several designs) is for the status LEDs. If set to (hypothetical) Treat Decals as LEDs allow a user to define the offset (from the center of the "key") and diameter of the hole.
In KLE you have the option to set a key as a "Decal" which per the KLE hovertext are "Purely Decorative." They even have a button specifically for creating a set of 3 decals for status lights (num, caps, and scroll locks). However when I copy my JSON into the web interface they are mistreated and standard switch holes are cut instead.
The JSON for decals contains the property
d:trueso a toggle to ignore keys with that attribute would be helpful.Alternatively, it could be a 3 way toggle since the most common use for decals (that I have seen across several designs) is for the status LEDs. If set to (hypothetical)
Treat Decals as LEDsallow a user to define the offset (from the center of the "key") and diameter of the hole.