Make the rotary encoder more responsive

[mwyborski]

The resolution 4 rotary encoder on my Keychron Q2 is missing a lot of ticks, when not all 4 pulses are detected. By putting a constraint on the default state 0xF of the encoder it is possible to catch a lot of these lost ticks and the performance of the rotary encoder improves noticeable and is reliable.

Description

Modified encoder_update to be more permissive about lost pulses when returning to the default state 0xF (no movement) to detect if a tick has happened. E.g. on resolution 4 rotary encoder all ticks with only 1, 2 or 3 detected pulses have been discarded in the original code, but when the rotary encoder returns to the recognized state of no movement and pulses are present, we can be sure, that a tick has happened. This PR catches all these lost ticks with only 1,2 or 3 pulses, which results in a more reliable performance of the rotary encoder.

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Issues Fixed or Closed by This PR

Rotary encoder losing a lot of ticks, when not all pulses have been recognized.

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).

[mwyborski]

This also fixes ENCODER_DEFAULT_POS problem with the encoder skipping pulses when it changes direction. I will submit a new PR with this in mind and make it only active if it is defined and keep the code backward compatible.

[tzarc]

Any particular reason you closed this? Accidental?

[mwyborski]

Hi!
The reason i closed this is because i modified the patch to be more compatible with the current approach and i made a new PR:
#16932