Alabastard

is the boards that are going over the memory limit expected? the code this adds to base without enabling anything is almost nothing...

Let me know if there is anything I can do to help the process along

Okay so a bit of a major update to how pointing mode maps are working. Pointing mode maps now use `action_exec` to process key presses (basically the same code as...

Okay should be cleaned up now. Sorry for anyone who picked it up while it was a bit of a mess for a bit there. _need to be better about...

Okay there was a bit more than documentation to fix up, but should be working as intended now. `POINTING_MODE_MAP_COUNT` is now properly handled automatically at compile time (i.e. not intended...

Argh another keyboard is going oversize again is this expected? (the code should not add much size without enabling things unless I missed something) Also what is keeping this code...

> First off, thank you very much, alabastard, this is great! You are very welcome! I am just happy when someone uses my code :) > I tested the changes...

Okay just pushed a conflict resolution patch due to the dip switch changes.

> "playing" with this PRs code, to see if&how a dpad feature would fit in here. > > while doing so, some refactoring/typo fixes/.../suggestions came together = [Alabastard#2](https://github.com/Alabastard/qmk_firmware/pull/2) feel free...

~@zvecr I thought I should ask as you mentioned in #22770 that there are a few things in this PR that you think could use a revamp and I was...