HaxeFlixel / HaxeFlixel/flixel
Holding down keyboard keys on MacOS brings up special character menu
Nobody has claimed this yet.
- Dominant language
- Haxe
- Stars
- 2.2k
- Forks
- 522
- Avg merge
- 34m
- Merged PRs (30d)
- 1
Description
- Haxe version: 4.2.5
- Flixel version: 5.6.2
- OpenFL version: 9.3.3-L3uoGG
- Lime version: 8.1.2
- Affected targets:
MacOS 14.0 (23A344) - Apple M1 Max
Code snippet reproducing the issue:
Any project with a window will reproduce it. For instance, running the default flixel tpl -n "HelloWorld" project.
Possibly relevant settings system:
I have the "ABC - Extended" keyboard layout selected.
Observed behavior:
If I hold down certain keys on the keyboard that have variants/accents (like the A key, for instance), then a menu will appear to the top-left of the window (if in windowed mode) or screen (if fullscreen).
Expected behavior:
Unless I'm specifically inputting into a text field, I would not want this menu to appear. And in those cases, were it to appear, I would want it to appear in the correct location. Asking for perfect behaviour might be too much, but I would much prefer the menu never appear, rather than its current behaviour.
It is also present in other haxe games, like Dead Cells, so there must be some similarities in window instantiation/app settings.
(looking for games/apps that don't exhibit this behaviour, uh, it's not haxe I think, but VVVVVV and Aseprite don't)
Possible links to people possibly struggling with the same problem that I stumbled across while I was trying to solve it myself (sometimes it manifests as people reporting that key-repeats aren't getting sent):
https://apple.stackexchange.com/questions/332769/macos-disable-popup-showing-accented-characters-when-holding-down-a-key
https://www.reddit.com/r/runescape/comments/atudk0/macbook_whenever_i_press_and_hold_a_key_an_accent/
https://github.com/bus-stop/Termination/issues/9
https://fsunuc.physics.fsu.edu/git/gwm17/glfw/commit/17a15a20f28ed95e0e69d403687416c023c77e7e
https://stackoverflow.com/questions/76546729/why-are-certain-repeated-keys-ignored-by-interpretkeyevents-in-nsresponder
https://fsunuc.physics.fsu.edu/git/gwm17/glfw/commit/17a15a20f28ed95e0e69d403687416c023c77e7e
https://github.com/smolck/uivonim/issues/106#issuecomment-782522713
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the default Flixel template on macOS, then trace the window instantiation and keyboard-input settings implicated by the report. No file or test is named; done means holding a key in a game window no longer opens macOS’s accent menu, while the expected text-field behavior remains acceptable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100