Qmk_firmware: Mouse movement on Ergodox EZ

[ajh3]

Using this keymap, on Ubuntu: https://configure.ergodox-ez.com/layouts/XEL4/latest/0

Mouse movement has several issues.

-Pressing down+right at the same time causes the cursor to lock in place.
-Pressing down+left at the same time causes the cursor to move left only.
-Pressing up+right at the same time causes the cursor to move up only.
-Pressing up+left at the same time is the only diagonal combination that works reliably as expected.

The above keymap places the mouse on a momentary-accessed layer, but I've tested this on the main layer and the behavior is exactly the same.

Side note, I recently tried an Ultimate Hacking Keyboard and the code they are using for mouse movement is far, far smoother than what QMK is using, and doesn't have any of these bugs, so that may be good to research.

I am not very experienced in C programming, although if someone can provide some suggestions on where to start debugging this, I am open to putting in some work to improve it.

[noroadsleft]

144 looks like it could be related, but I can't actually worked out if this was for sure solved/fixed.

Tagging @ezuk in hopes he can be of more help.

[drashna]

There was actually a fix for this about 3 months ago, actually. I don't think the Ergodox EZ Configurator has that commit.

If you grab the C file from there and compile from source, it may fix the issue that you're seeing.

[noroadsleft]

Also

https://config.qmk.fm/#/ergodox_ez/LAYOUT_ergodox

[fdidron]

@ajh3 The online configurator is indeed lagging behind, we are going to update the QMK dependency in the coming weeks. In the meantime, I compiled your layout against QMK's master branch and as @noroadsleft and @drashna mentioned, it fixed the issue. You can download the hex file and modified source file from here: aaron_qmk_master.zip

[ajh3]

Thanks everybody for the help! I got the build environment set up and was able to build the firmware too based on your changes @fdidron. Would you mind explaining why it is required to change KEYMAP to LAYOUT_ergodox in the newer version?

Is there a difference feature-wise in that QMK.fm configuration tool vs. the Ergodox EZ configurator (aside from more up-to-date dependencies), or is the latter just a prettier UI?

[noroadsleft]

I can't answer the second question (because I don't know the answer fully), but as to the first:

The switch from KEYMAP to LAYOUT_ergodox was one of terminology. QMK is trying to use LAYOUT to describe the physical arrangement of the keys, and KEYMAP to describe what happens when a key is pressed. Using KEYMAP to describe the physical arrangement is a deprecated usage that QMK is trying to do away with.

LAYOUT_ergodox specifically allows keymaps to be used on multiple keyboards that share a form factor. https://docs.qmk.fm/#/feature_layouts

[drashna]

Is there a difference feature-wise in that QMK.fm configuration tool vs. the Ergodox EZ configurator (aside from more up-to-date dependencies), or is the latter just a prettier UI?

Basically that. There are some other differences, like being able to set the RGB colors, which the QMK Configurator doesn't support, currently.

[drashna]

@ajh3 would you mind if I closed this?

[ajh3]

@drashna Go right ahead, and thanks for the info.

For future reference, is this the right place to open issues about the Ergodox EZ and its configurator, specifically?

Also, where are updates to the EZ configurator tracked? The website itself doesn't seem to mention what version of the QMK dependencies it is using.

[ezuk]

@ajh3 can always just ping us over email, [email protected] -- we're pretty quick over there :)

[drashna]

@ajh3 for general QMK stuff, yes. And if you're using the QMK Configurator. And general issues.

If you're using the Ergodox EZ Configurator, then ... well, both here and contacting ezuk or whomever with the email listed above is a good idea.