Closed minego closed 7 years ago
Yeah, this would be really nice. This is the biggest issue with mapping the left/right shift key to delete/backspace respectively -- you can't do shift-click to select without it also generating a 'delete' key immediately after (or backspace depending on which shift key you used).
This was fixed by commit f69c5a3. It has not been included in a release yet, so if you want this fix, you will probably (unless your distro has an xcape-git package) need to compile xcape yourself as detailed in the README.
Awesome! I can't wait to try it out. Thank you.
On Sep 26, 2016 10:54 AM, "yut23" notifications@github.com wrote:
This was fixed by commit f69c5a3 https://github.com/alols/xcape/commit/f69c5a3f2b54bd812da99bb8ff61e86377f441f2. It has not been included in a release yet, so if you want this fix, you will probably (unless your distro has an xcape-git package) need to compile xcape yourself as detailed in the README.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/alols/xcape/issues/66#issuecomment-249628975, or mute the thread https://github.com/notifications/unsubscribe-auth/AAcoiJiiU6rfph7uVY9RtvRpRndTS_Fhks5qt_jbgaJpZM4Hr6ha .
It appears to be working perfectly. Thank you.
If I press control, click with the mouse, and then release it the mouse event will work as a control+click AND an escape keypress will be sent. I would like a mouse click to be treated like another keypress, and prevent sending escape.
This is not a huge problem, but in some applications that use control+click it can cause confusion. I noticed this while playing a game. A control+click (which is used heavily in the game) caused the menu to pop up because of the escape key event.