[GH-ISSUE #1926] [Feature Request]: QoL on Multi-Keymap #1268

New issue

Closed

opened 2026-03-03 19:05:22 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 19:05:22 +03:00

Owner

Originally created by @SwampertX on GitHub (Jul 19, 2025).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1926

Originally assigned to: @TheMoonThatRises on GitHub.

Really excited to see #1567 merged! There are a few QoL suggestions for multi-keymaps:

Pop-up window is closed every time a new keymap is created.
Importing a keymap gives a text field, which is so cryptic. Should it be a file selection UI instead?
There is no documentation yet for multi-keymap.
It seems to me that cmd+] is more commonly associated with "next" and cmd+[ with "previous"?
The order of keymaps seem arbitrary to me. We should be able to arrange them.

Describe the solution you'd like

Save the state of keymaps after successful addition but keep the pop-up keymap window open.
Perhaps let's use a file selection UI?
It would be great if we have documentation, let me know if you need help.
Maybe swap cmd+[ with cmd+]?
Add option for arranging keymap orders for easier navigation (instead of cycling through!) Even better, we could map some chords (eg cmd + shift + any key) to switching between keymaps.

Anything else?

Tagging @TheMoonThatRises, thanks for the awesome and much-awaited feature!

Unfortunately I don't know Swift and Mac dev, so I can't hack it right now.

Issue Language

Yes my issue is written in English

Originally created by @SwampertX on GitHub (Jul 19, 2025). Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1926 Originally assigned to: @TheMoonThatRises on GitHub. ### Is your feature request related to a problem? Really excited to see #1567 merged! There are a few QoL suggestions for multi-keymaps: <img width="504" height="359" alt="Image" src="https://github.com/user-attachments/assets/5f8f0eb0-c412-4ff6-b948-d85942fe7c10" /> 1. Pop-up window is closed _every_ time a new keymap is created. 2. Importing a keymap gives a text field, which is so cryptic. Should it be a file selection UI instead? 3. There is no documentation yet for multi-keymap. 4. It seems to me that cmd+] is more commonly associated with "next" and cmd+[ with "previous"? 5. The order of keymaps seem arbitrary to me. We should be able to arrange them. ### Describe the solution you'd like 1. Save the state of keymaps after successful addition but keep the pop-up keymap window open. 2. Perhaps let's use a file selection UI? 3. It would be great if we have documentation, let me know if you need help. 4. Maybe swap cmd+[ with cmd+]? 5. Add option for arranging keymap orders for easier navigation (instead of cycling through!) Even better, we could map some chords (eg cmd + shift + any key) to switching between keymaps. ### Anything else? Tagging @TheMoonThatRises, thanks for the awesome and much-awaited feature! Unfortunately I don't know Swift and Mac dev, so I can't hack it right now. ### Issue Language - [x] Yes my issue is written in English

kerem

2026-03-03 19:05:22 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-03 19:05:23 +03:00

Author

Owner

@TheMoonThatRises commented on GitHub (Jul 26, 2025):

Thank you so much for the feedback! Below address the points that you bring up.

I completely agree, I will work on a fix for that.
I believe the text field is cryptic for you because the strings have not been localized for you. The text field is there for the user to name the keymap, and then the file selector UI appears afterwards. Do you suppose it should be in the opposite order?
Documentation in PlayBook? PlayBook has been outdated since version 2.0.5, and I think it would be great to have it updated. Help would be appreciated getting PlayBook updated to 3.1.0.
You are completely correct, I'm not sure why those got switched...
Great idea.

@TheMoonThatRises commented on GitHub (Jul 26, 2025): Thank you so much for the feedback! Below address the points that you bring up. 1. I completely agree, I will work on a fix for that. 2. I believe the text field is cryptic for you because the strings have not been localized for you. The text field is there for the user to name the keymap, and then the file selector UI appears afterwards. Do you suppose it should be in the opposite order? 3. Documentation in PlayBook? PlayBook has been outdated since version 2.0.5, and I think it would be great to have it updated. Help would be appreciated getting PlayBook updated to 3.1.0. 4. You are completely correct, I'm not sure why those got switched... 5. Great idea.

kerem referenced this issue

2026-03-03 19:09:15 +03:00

[PR #1269] [MERGED] Adding develop changes to stable #1840

kerem referenced this issue

2026-03-03 19:09:15 +03:00

[PR #1270] [MERGED] Updating ymls #1841

kerem referenced this issue

2026-03-03 19:09:15 +03:00

[PR #1268] [MERGED] Add catch-all options to APP- and GAME-SUPPORT and append chip models to README #1842

kerem referenced this issue

2026-03-03 19:09:15 +03:00

[PR #1271] [MERGED] Updating yml #1843