Jamie Larkby-Lahet

I've tested to confirm the path name issue is resolved with evdev-0.12.2.

this is the config I've been using. the basic functionality is fine, but the "disable mouse layer when typing" is sticky. frequently the mouse layer won't re-enable after an early...

thanks for commenting. I wasn't sure if anyone else actually found it useful. I'm stuck right now because when the layer is disabled by typing it's reactivation is unreliable. since...

somewhat unrelated, but: i thought it would be nice to use the capslock LED to indicate that the automouselayer is active. however once kanata captures the keyboard, I can no...

I definitely haven't seen any crashes that I'm aware of. the only time comparison I've added is here https://github.com/jtroo/kanata/pull/1080/files#diff-428b2d4ad36aba907ce64670e822d08895db03b69b73f826d6155f218c114092R74-R75 and it doesn't directly compare 2 timestamps, but rather a time...

I think it makes sense to use the SystemTime timestamp of the event, rather than timestamping when kanata gets around to processing it. functionally, the only difference seems to be...

fair enough. I implemented a new version to go with your sugestion to use `hold-for-duration`. this works perfectly and is a simpler implementation without added timestamp tracking. https://github.com/wolfwood/kanata/tree/feature/automousekeys-simple only issue...

example config ``` (defsrc) (defvirtualkeys mouse (layer-while-held mouse-layer) ) (defalias mhld (hold-for-duration 750 mouse) moff (on-press release-vkey mouse) _ (multi @moff _ ) ) (deflayermap (base) F24 @mhld ) ;;...

I guess `hold-for-duration` isn't actually aware that the virtual key has been released, so its timer is just reset, rather than triggering the press event again. makes sense.

I fixed the old PR to use `Instant` for posterity, but I have opened a new PR #1598 expanding on my earlier simplified approach which is far superior. using `hold-for-duration`...