Skip to content

fix(keyboard): render fn as a single keycap - #132

Merged
esphynox merged 1 commit into
mainfrom
fix/fn-key-double-render
Aug 25, 2026
Merged

fix(keyboard): render fn as a single keycap#132
esphynox merged 1 commit into
mainfrom
fix/fn-key-double-render

Conversation

@esphynox

@esphynox esphynox commented Aug 25, 2026

Copy link
Copy Markdown
Collaborator

Summary

Fix duplicate and inconsistent fn rendering by moving it to a single state-driven path.

Tests

  • tuist generate
  • xcodebuild test -project Keyty.xcodeproj -scheme Keyty -destination 'platform=macOS' — 301 tests, 0 failures
  • Other: tuist generate not needed — no change to Project.swift, dependencies, build settings, resources, or project structure

UI Changes

No screenshots attached, but there are two visible changes:

  • A single fn press now shows one keycap that lights on press and dims on release,
    instead of two separate keycaps.
  • fn picks up the special-key theme instead of the modifier theme, following from it no
    longer sitting in the modifier row. Say the word if the modifier colors should be kept
    and the category mapping can be restored on its own.

Documentation

  • Updated relevant docs
  • No docs needed

Release Notes

Pressing fn now shows a single keycap instead of rendering it twice, and it is styled
like the other special keys.

@esphynox esphynox added the bug Something isn't working label Aug 25, 2026
@esphynox esphynox self-assigned this Aug 25, 2026
@esphynox
esphynox merged commit d7d515f into main Aug 25, 2026
1 check passed
@esphynox
esphynox deleted the fix/fn-key-double-render branch August 25, 2026 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant