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.

Sign up for GitHub

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

Jump to bottom

remove non-existent method from ploopy documentation #19957

Merged
merged 3 commits into from
Feb 28, 2023
Merged

remove non-existent method from ploopy documentation #19957

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2979ca6
remove non-existent method from ploopy documentation
ftc Feb 27, 2023
51686cf
fix indent style
ftc Feb 27, 2023
dca62c5
apply suggestions from discord user elpekeñin
ftc Feb 28, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 6 additions & 9 deletions keyboards/ploopyco/trackball/readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,20 +29,17 @@ The PCB should indicate which revision this is.

While the defaults are designed so that it can be plugged in and used right away, there are a number of things that you may want to change. Such as adding DPI control, or to use the ball to scroll while holding a button. To allow for this sort of control, there is a callback for both the scroll wheel and the mouse sensor.

The default behavior for this is:

```c
void process_wheel_user(report_mouse_t* mouse_report, int16_t h, int16_t v) {
mouse_report->h = h;
mouse_report->v = v;
}

void process_mouse_user(report_mouse_t* mouse_report, int16_t x, int16_t y) {
mouse_report->x = x;
mouse_report->y = y;
report_mouse_t pointing_device_task_user(report_mouse_t mouse_report){
// executed each time the sensor is updated
// mouse_report.<attribute> - can be used to access indivdual mouse attributes
return mouse_report;
}
```

More information on `report_mouse_t` may be found [here](https://docs.qmk.fm/#/feature_pointing_device?id=manipulating-mouse-reports).

This should allow you to more heavily customize the behavior.

Alternatively, the `process_wheel` and `process_mouse` functions can both be replaced too, to allow for even more functionality.
Expand Down