Customizing mouse speed / dragscroll speed

[kindred scroll]

Hey folks ! I'm using the miyoku zmk fork, and trying to customize the mouse speed setttings. I'm building based on victorlucachi/zmk/pmw3610, but I'm not sure where the original code comes from, and they're not familiar with mouse speed customization.

Using a trackball on my charybdis nano.

I changed those in miryoku_kludge_mousekeyspr.h:

#define U_MOUSE_MOVE_MAX 350
#define U_MOUSE_MOVE_EXPONENT 1
#define U_MOUSE_MOVE_TIME 350
#define U_MOUSE_MOVE_DELAY 0
#define U_MOUSE_SCROLL_MAX 3
#define U_MOUSE_SCROLL_EXPONENT 1
#define U_MOUSE_SCROLL_TIME 50
#define U_MOUSE_SCROLL_DELAY 0

But it does not seem to change anything.
Anyone have any insight into that ?

Here is also a link to my miryoku zmk fork:
https://github.com/bstiq/miryoku_zmk/tree/charybdis-test

[kindred scroll]

EDIT: it seems those are for mousekeys only, not trackball. I'll take a further look

[kindred scroll]

seems like it's hard coded 😩 cc @iron heath

cc @thorn mountain

[iron heath]

It should really be using Kconfig or devicetree for that. See https://zmk.dev/docs/config.
You could fork and make changes, then update the zmk line in the outboard, or use the workflow branches field, to build from your fork. But if you're making code changes to ZMK it'd be better to build locally instead.

[kindred scroll]

hmmm yeah I have no idea how to do any of those

so I'll leave it for now 😄

actually scrap that I have a vague idea of how to, but other projects ongoing

[iron heath]

The minimum change is to fork https://github.com/victorlucachi/zmk/tree/pmw3610-aml, edit the definition of the constant in that branch, push your changes, and edit https://github.com/manna-harbour/miryoku_zmk/blob/charybdis-test/.github/workflows/build-example-tbkmini-nice_nano_v2.yml and append

      branches: '["bstiq/zmk/pmw3610-aml"]'

to have the workflow build from your fork.

[kindred scroll]

thank you ! let me try that once I'm done dealing with that russian (and bookkeeping... so, this weekend)

[kindred scroll]

hmmm, I'm using in charybdis.c:

outboard_repository=victorlucachi/zmk-config-charybdis
outboard_ref=main
outboard_from=config
outboard_to=boards/shields/charybdis

zmk=victorlucachi/zmk/pmw3610

should I not change it to my repo on that last line instead of in the tbk mini yml ?

let me try that anyway

[kindred scroll]

hmm, does not seem to make a difference, let me try different values

[iron heath]

You could change it there instead. That's the default for all workflow builds for that keyboard. Using the branches workflow option will override it just for that workflow.

[kindred scroll]

hmmm yeah I updated both files, then tried changing the scroll div factor (went from 2 to 200), nothing changed to the dragscroll

so either I didn't configure the build correctly, or I don't understand the code

[iron heath]

The workflow option will override the outboard, so changing one is sufficient, but changing both won't hurt.
If you enable workflow debugging https://github.com/manna-harbour/miryoku_zmk#workflow-builds and run a new build, then check this step in the logs https://github.com/bstiq/miryoku_zmk/actions/runs/5609405970/job/15196949088#step:4:163, you'll be able to see the ZMK fork in use.

[iron heath]

You can see which files are being built from here https://github.com/bstiq/miryoku_zmk/actions/runs/5609405970/job/15196949088#step:6:234. But without needing to enable debugging or check the logs, you can add a bogus line to the file and see if the build fails. Also consider building locally.

[kindred scroll]

oh well I added some random text in the files and the build didn't fail

so there's that

I changed both config files so I'm not sure what's happening

[thorn mountain]

try changing it here? https://github.com/bstiq/zmk/blob/9911dacfc4bd4e82b73ab403b4f6f566d6c67b51/app/dts/behaviors/trackball.dtsi#L64C15-L64C15

[kindred scroll]

well I added some random blobs that should break compilation in the files and it doesn't

so my miryoku zmk doesn't point to my zmk somehow

I did leave outboard_repository=victorlucachi/zmk-config-charybdis in the shields/charybdis file but that's it

I pointed everything else to my zmk fork

[thorn mountain]

as far as I can tell your recent changes are to a board definition thats not being used for the build

[thorn mountain]

give this a go. who knows, it might work

[kindred scroll]

sure

[kindred scroll]

hmm

let me enable the debug thing like manna mentioned as well

[thorn mountain]

how's it been, other than the dragscroll inconvenience? have you been daily using the wireless cnano?

[kindred scroll]

ok, running now

[kindred scroll]

I feel the mouse cursor is not very smooth when using wireless

well, I know for sure

but sometimes it goes back smooth

with central wired is never an issue

other than that, the dragscroll is annoying

but that's it, it's functionally identical to my wired splinky cnano

oh, also when not using the trackball for more than a few seconds, it still needs a few hundreds ms to "wake up from sleep", I'd like to make that less noticeable

[thorn mountain]

yeah, with it wired its really smooth. I've only had stuttery tracking either when I increased the distance between the keyboard and the ble receiver, or when there's a bunch of bluetooth devices around

[kindred scroll]

oh hmm, I do have my phone playing music through bluetooth next to it

interesting

allright the build worked, let's check the logs

[thorn mountain]

I've been switching keyboards for the past few days, and yeah, going back to the charybdis I had this happen too, but I dont find it that annoying. I think the benefits of having a wireless keyboard thats really power efficient outweigh the cons

[kindred scroll]

hmm, it seems to point towards the right zmk repo

let me flash it with the changes you mentioned

[kindred scroll]

well power efficient.... I still need to find a way to slap a big battery in there

[thorn mountain]

nice. did you change it to something ridiculous, that would be really obvious? haha

[thorn mountain]

yeah. if you manage to somehow make it run on regular cells, that would be insane. just swap the batteries out when they're depleted

[kindred scroll]

50 instead of 10

nope, same

[thorn mountain]

hmmm

are you using tsl or tsl_fine in your keymap, or build options (still confused on miryoku workflows)?

if its the latter, try changing this too https://github.com/bstiq/zmk/blob/979e960e196e31ffaca3ae75c64aa12106bb1999/app/dts/behaviors/trackball.dtsi#L85

[kindred scroll]

tsl fine

allright

though lately I really feel I could use a standalone trackball

[iron heath]

@kindred scroll Yeah, you were editing app/boards/arm/nrfmacro/trackball/trackball.c, which is for a different keyboard, and so isn't being used here.

[kindred scroll]

I was editing trackball_new.c as well

mostly because that's the only place I could find anything about dragscroll 😅 no idea what I'm doing here

oh hey, I changed the fine scale factor from 1 to 50 and it's better !

I will put it back to something more reasonable

is there not a way to modify that value directly in my miryoku fork rather ?

[iron heath]

@kindred scroll But since the speed is in a devicetree file, you'll be able to adjust without needing a ZMK fork. But try editing in the fork for now as it'll be simpler to get working.

[kindred scroll]

yes editing in my miryoku fork sounds way easier

I don't know what a devicetree file is but I can follow instructions

I'm now trying 5 to see how well that works

hmmm, it seems to work fine with 5, but I have to set the amount of lines I scroll with the mouse at a time to 1

it's also way less smooth than on my wired one

but it works !

thanks for the help