Custom keymaps for my QMK keyboards https://code.ryuslash.org/my-keymaps/atom?h=main 2026-01-21T08:36:15Z 2026-01-21T08:36:15Z Tom Willemse 2026-01-21T08:36:15Z urn:sha1:5a18c750ef29783ccc340bd458ec3eb73c9ed632 2026-01-21T08:16:54Z Tom Willemse 2026-01-21T08:16:54Z urn:sha1:06766085fd195165222fa1b797678f56e1dfb2ed 500 was too low, kept missing too many keys. Now trying 750. 2026-01-17T20:37:09Z Tom Willemse 2026-01-17T20:34:45Z urn:sha1:1723ddcf87a7083250713db797e0269195909833 I'm doing a binary search of the right setting here. I've used the highest setting for a while and it's just too slow, so now I've cut it in half. If this is too fast then I'll move to 750 and see how it goes. 2026-01-17T20:37:09Z Tom Willemse 2026-01-17T19:33:37Z urn:sha1:9e862f4b5d1eac668153712e6ff6a51633907983 This way they align with the , and . keys, and switching between tabs and desktops lines up with eachother, so it's just a different modifier that's used. 2025-09-16T04:23:42Z Tom Willemse 2025-09-16T04:23:42Z urn:sha1:da501f6153d39f33c62be36596674a4acf435ff4 Couldn't get used to natural scrolling there either. 2025-09-13T05:42:37Z Tom Willemse 2025-09-13T05:42:37Z urn:sha1:45cad9d30b4df052c2130103ecd49c24ad799049 Used by Sawfish to open the main menu, for example. 2025-09-13T05:41:46Z Tom Willemse 2025-09-13T05:41:46Z urn:sha1:98286786fdbd8d28ab155dfadf729ebf65617534 I can't get used to the natural scroll of pushing the ball down, but the screen going up. I prefer the two to be the same. 2025-09-13T01:04:11Z Tom Willemse 2025-09-13T01:04:11Z urn:sha1:9aacf90e6c9f0f1f856dabd1006a24804c40aebc Pressing and holding this button will change the mode of the track ball from moving the mouse to scrolling. 2025-09-12T23:25:30Z Tom Willemse 2025-09-12T23:15:13Z urn:sha1:64781857c85c67c24eef122dd537eff5cbc3bfb9 This makes it easier to see what's going on and if this have to move around that requires fewer changes as well. 2025-09-12T23:25:21Z Tom Willemse 2025-09-12T23:10:56Z urn:sha1:3f936d71716abbb32a1fdcae904793209eaa4a8e - Enable auto mouse mode. This is necessary so that when I move the trackball it automatically switches to the layer with the mouse keys. - Set a long time out to switch off the mouse layer. Since I'm just getting used to this I'll start with a long time out and then tweak it as I like. 1000 was the highest recommended value according to the documentation. - Add a mouse button layer to my layout. This only has the mouse buttons 1 and 2 for now, but I'll adjust as I try it out. It also has no way to access it other than with the auto mouse mode feature. - Add ‘pointing_device_init_user’ function. This function must call ‘set_auto_mouse_enable’ because the auto mouse feature can be toggled on and off at runtime and it's off by default. This enables it when the pointing device is initialized. It also calls the ‘set_auto_mouse_layer’, which can also be done in the ‘rules.mk’ file, but here I can make sure that what I define as the mouse layer will always be what's called, even if the layer numbering changes. - Enable the pointing device feature, set it to ‘navigator_trackball’, which is the ZSA trackball that attaches to the Voyager. This requires the ZSA fork of QMK to work, since the navigator device hasn't been pulled into the main QMK repository yet. - Enable the mouse key feature. This is necessary to be able to use mouse keys such as the mouse buttons 1 and 2.