Skip to content

Conversation

@lesshonor
Copy link
Contributor

@lesshonor lesshonor commented Dec 4, 2024

Enabling Studio by default precludes successful settings_reset builds, and keymap changes made via compiling and flashing are henceforth ignored.

  • Users who remove the &studio_unlock keybinding while customizing may find themselves unable to unlock their keyboards so they can put it back.
  • A sudden move to Studio could be an unpleasant surprise to many who are currently using Keymap Editor as their keymaps suddenly stop updating, particularly if those keymaps incorporate the many things Studio doesn't understand yet.
    • It's noted in the readme, but adding the reserved layers already turns the keymap into something Keymap Editor can't interpret.

Much like Studio-by-default, some of the settings in alu40_defconfig could also result in extended troubleshooting from helping hands in the ZMK discord who do not expect these settings to be turned on at the board level. These have been moved under config/alu40.conf.

This breaks settings_reset builds, and will prevent compiled keymap
updates from taking effect for non-Studio users.
- Increasing TX power is not always necessary
- Keycodes like C_AL_CALC won't work if the basic consumer page is used
Allow users to fork this repo and delete the board definition in order
to get started, as there is no standalone user-config repo.
@ReFil
Copy link
Contributor

ReFil commented Dec 21, 2024

Thanks for doing this, sorry it took a while to look at it, i didn't spot any notification from GitHub about it

@ReFil ReFil merged commit 531064a into PolarityWorks:main Dec 21, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants