kemonine/keyboard
kemonine/keyboard
1
0
Fork 0
Code Issues Pull requests Releases 2 Activity
keyboard/qmk/keyboards/ploopyco/mouse/readme.md
kemonine 089047d1e3 Update qmk sources
2020-12-25 15:21:40 -05:00

2.7 KiB
Raw Blame History

Ploopyco Mouse

Ploopyco Mouse

It's a DIY, QMK Powered Mouse!!!!

Make example for this keyboard (after setting up your build environment):

make ploopyco/mouse:default:flash

To jump to the bootloader, hold down "Button 4" (the "forward" button on the left side)

See the build environment setup and the make instructions for more information. Brand new to QMK? Start with our Complete Newbs Guide.

Customzing your PloopyCo Mouse

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

The default behavior for this is:

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;
}

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.

Additionally, you can change the DPI/CPI or speed of the krackball by calling pmw_set_cpi at any time. Additionally, there is a DPI_CONFIG macro that will cycle through an array of options for the DPI. This is set to 1200, 1600, and 2400, but can be changed. 1600 is also set to the default.

To configure/set your own array, there are two defines to use, PLOOPY_DPI_OPTIONS to set the array, and PLOOPY_DPI_DEFAULT.

#define PLOOPY_DPI_OPTIONS { 1200, 1600, 2400 }
#define PLOOPY_DPI_DEFAULT 1

The PLOOPY_DPI_OPTIONS array sets the values that you want to be able to cycle through, and the order they are in. The "default" define lets the firmware know which of these options is the default and should be loaded by default.

The DPI_CONFIG macro will cycle through the values in the array, each time you hit it. And it stores this value in persistent memory, so it will load it the next time the device powers up.