mirror of
https://github.com/PlayCover/PlayCover.git
synced 2026-04-26 00:05:52 +03:00
[GH-ISSUE #1098] Keyboard can’t be used in the app #602
Labels
No labels
UI
app-support
bug
bug
documentation
duplicate
enhancement
game-support
good first issue
help wanted / caution
inactive
invalid
macos-beta
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/PlayCover#602
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @MoeNyanSakura on GitHub (Sep 16, 2023).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1098
Describe the bug
My laptop is Macbookair Sonoma14.0(bata)
PLAYCOVER 3.00,2.0.5
In the game I can’t use the keyboard to control the characters in the game(yuanshen) Although I have set up the keyboard map,but it still doesn’t work
I have let the system allow the keyboard using of playcover.
Steps to reproduce
As the passage below(My laptop is Macbookair Sonoma14.0(bata)
PLAYCOVER 3.00,2.0.5
In the game I can’t use the keyboard to control the characters in the game(yuanshen) Although I have set up the keyboard map,but it still doesn’t work
I have let the system allow the keyboard using of playcover.)
The bug that let me almost can’t do everything with the game,It just like the keyboard doesn’t’t give me any response at all
The keyboard map setting that I can’t change the wasd into any other buttons
Expected behaviour
I just want you to fix the bug,so that I can you the keyboard to control the character ,thank you
Crash log
No response
What version of PlayCover are you using?
Nightly/beta
What version of macOS are you using?
macOS beta (please state the specific version)
Issue Language
@MEMORIEmusic commented on GitHub (Sep 16, 2023):
Same as #1048. Read my comment