qmk/qmk_firmware

[Bug] Odd behavior with KC_SFTENT

Open

#8,023 opened on Jan 27, 2020

View on GitHub
 (4 comments) (0 reactions) (0 assignees)C (43,867 forks)batch import
bughelp wanted

Repository metrics

Stars
 (20,368 stars)
PR merge metrics
 (Avg merge 20d 9h) (27 merged PRs in 30d)

Description

This bug report is just addressing some findings I've done with the KC_SFTENT, which leads me to think that it is not working entirely as intended. I have been able to mitigate my own issues, and since I don't find more posts about it, we're probably not looking at a huge problem. But anyways:

I have set my Preonic Rev3 up with a KC_SFTENT key. In most situations it behaves just as intended (tap for enter, hold for right shift). But in a few pieces of software I get some strange behavior. The two programs I have found to be affected are Red Dead Redemption 2 on Windows 10 and Alfred (the Spotlight replacement) on macOS Catalina.

In Red Dead Redemption 2, the enter functionality is sparse. It often coincides with the fact that the game wants me to press and hold enter, for some functionality, which of course doesn't work with KC_SFTENT. But in some situations it doesn't register a regular tap for enter as it should. Mostly mitigated by reassigning the key, within the game.

In Alfred, whenever I hover over a file or app (or something that can show a preview) in Alfred and tap for enter. It yields the functionality of me tapping shift, which results in showing the file/app preview instead of the intended opening/executing that the press of enter should result in. Mitigated by disabling the preview functionality of Alfred.

If there's any debug information I can provide, please let me know.

System Information

  • Keyboard: Preonic
    • Revision: 3
  • Operating system: Windows 10 (latest stable build), macOS Catalina (latest stable)
  • Firmware built with QMK configurator on Dec 12, 2019, see my repo.

Contributor guide