Add keyboard level encoder function

[waffle87]

Description

Added a keyboard level encoder function as many users have complained about losing encoder functionality when using QMK Configurator.

Types of Changes

• Keyboard (addition or update)

Checklist

• My code follows the code style of this project: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[jordysamuel]

If encoder behavior is already determined in the keymap, pro.c interferes with the encoder behavior. I updated my branch to the latest master and my encoder configured for brightness started sending volume up and down as well.

[gourdo1]

@drashna @waffle87 Is there a workaround for keymaps that already have advanced encoder functions and layers? As is, this blanket applies an additional volume up/down across all layers. It can't be shut off, since "ENCODER_ENABLE = yes" is defined in rules.mk one directory up (in /ANSI), so I'm not sure I can affect it from inside my keymaps folder hierarchy.

[jordysamuel]

@drashna @waffle87 Is there a workaround for keymaps that already have advanced encoder functions and layers? As is, this blanket applies an additional volume up/down across all layers.

I just commented out the code in pro.c so it becomes a blank file. For now that seems to be the only way.

[fauxpark]

You can just set ENCODER_ENABLE = no in your keymap rules.mk.

[tzarc]

Or, if you still want encoder functionality return false; at the end of your keymap's encoder_update_user().

[gourdo1]

Or, if you still want encoder functionality return false; at the end of your keymap's encoder_update_user().

@tzarc Thanks, this worked for me.