Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] HE Profile switch ( FN + P + ZXC ) does not use the User-Defined Position por FN #325

Open
2 tasks
MarioRicalde opened this issue Nov 10, 2024 · 1 comment
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@MarioRicalde
Copy link

Describe the Bug

As the title describes:

  1. Move the position of the FN key that comes by default to the right of the space bar.
  2. Attempt to trigger the Profile Switch by pressing the combo using the new FN position.
  3. Nothing happens.

What works:

If you use the original position of the key works, but it will send whatever keys are assigned.

Please fix 🙏

Keyboard Used

keychron/q3_he/ansi_encoder:default

Link to product page (if applicable)

No response

Operating System

No response

qmk doctor Output

No response

Is AutoHotKey / Karabiner installed

  • AutoHotKey (Windows)
  • Karabiner (macOS)

Other keyboard-related software installed

No response

Additional Context

No response

@MarioRicalde MarioRicalde added bug Something isn't working help wanted Extra attention is needed labels Nov 10, 2024
@PeterMortensen
Copy link

PeterMortensen commented Nov 13, 2024

Are you sure it was on the correct layer? -

  • Layer 2 and 3: Windows
    • Layer 2: Base layer
    • Layer 3: Fn key layer
  • Layer 0 and 1: Mac
    • Layer 0: Base layer
    • Layer 1: Fn key layer

How did you remap the key? Using Via? Using the Via clone? In QMK itself?

If using QMK, are you sure you compiled the firmware corresponding to the change in the keymap? There are two folders with keymaps, default and via

What file did you change, and what was the exact compilation step?

References

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants