Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix kinetic mouse mode #16950

Closed
wants to merge 1 commit into from
Closed

Fix kinetic mouse mode #16950

wants to merge 1 commit into from

Conversation

yorickpeterse
Copy link

@yorickpeterse yorickpeterse commented Apr 27, 2022

Description

Kinetic mouse mode is currently broken, as described in #12082 and #13711.

The PR #11766 introduced a set of fixes in early 2021. This PR was closed in favour of ongoing refactoring of QMK's mouse code (see #11766 (comment) and #12082 (comment)).

Since the mentioned comments, it appears nothing has been merged in order to fix kinetic mode, meaning kinetic mode is still broken. This commit adopts the changes from the pull request that was originally supposed to fix the problem, and updates the changes to handle recent changes to the mousekey.c file.

These changes have been tested with my personal keyboard, and result in kinetic mode working as advertised.

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

Fixes #12082
Fixes #13711

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.
  • I have read the CONTRIBUTING document.
  • I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Kinetic mouse mode is currently broken, as described in
#12082 and
#13711.

The PR #11766 introduced a set
of fixes in early 2021. This PR was closed in favour of
ongoing refactoring of QMK's mouse code (see
#11766 (comment)
and #12082 (comment)).

Since the mentioned comments, it appears nothing has been merged in
order to fix kinetic mode, meaning kinetic mode is still broken. This
commit adopts the changes from the pull request that was originally
supposed to fix the problem, and updates the changes to handle recent
changes to the mousekey.c file.

These changes have been tested with my personal keyboard, and result in
kinetic mode working as advertised.

Co-Authored-By: Jan Christoph Ebersbach <jceb@e-jc.de>
@github-actions github-actions bot added the core label Apr 27, 2022
@yorickpeterse
Copy link
Author

I noticed the documentation states to not use master branches for pull requests. Does that also apply in the case of a fork? If so I can change the branch 😃

@zvecr zvecr added the bug label Apr 27, 2022
@drashna
Copy link
Member

drashna commented Apr 27, 2022

Yes to both. This should target the develop branch, as it is definitely a behavior change, and we recommend not working from your master branch as it may make things more difficult when updating your fork.

@yorickpeterse
Copy link
Author

@drashna In this case the fork is set up specifically for these changes, my own fork lives elsewhere. Either way, I'll see if I can change the source branch 😃

@yorickpeterse yorickpeterse changed the base branch from master to develop April 27, 2022 19:01
@yorickpeterse
Copy link
Author

It seems I have to recreate the pull request with the new source branch, so I'll do that.

@yorickpeterse
Copy link
Author

New pull request is here: #16951

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants