Merge the custom_keys enum on annepro2.h with the AP2KeyCodes, so that the AP2_SAFE_RANGE on the end of the enum can be treated as an actual safe range.
Description
Currently the AP2_SAFE_RANGE is conflicting with the values on the custom_keys on annepro2.h and this forces people who want to make custom new keys to resort to workarounds such as using AP2_SAFE_RANGE + 10 (which kind of defeats the purpose of having a SAFE_RANGE after all).
This change is aimed at fixing this so the user can use AP2_SAFE_RANGE safely.
Types of Changes
[ ] Core
[X] Bugfix
[ ] New feature
[ ] Enhancement/optimization
[ ] Keyboard (addition or update)
[ ] Keymap/layout/userspace (addition or update)
[ ] Documentation
Issues Fixed or Closed by This PR
Checklist
[X] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Merge the custom_keys enum on annepro2.h with the AP2KeyCodes, so that the AP2_SAFE_RANGE on the end of the enum can be treated as an actual safe range.
Description
Currently the AP2_SAFE_RANGE is conflicting with the values on the custom_keys on annepro2.h and this forces people who want to make custom new keys to resort to workarounds such as using AP2_SAFE_RANGE + 10 (which kind of defeats the purpose of having a SAFE_RANGE after all).
This change is aimed at fixing this so the user can use AP2_SAFE_RANGE safely.
Types of Changes
Issues Fixed or Closed by This PR
Checklist