ihhub
Add a popup window for hotkeys info/menu by pressing a keyboard key
Preliminary checks
- [X] I've checked that there aren't other open issues on the same topic.
Describe the problem requiring a solution
It would be nice to have when you right click on buttons and such, displays the available hotkey, if it has one. Though it might not look as nice but the right click context text is only something that you use when you need information about it. Having this info easly accessible when just doing a right click, might suggest to a player not using hotkeys or use hotkeys that are not used as often. Hotkeys are a QoL for games and making them more accessible would improve the overall player experience.
A mockup of what I suggest. Though maybe the hotkey itself should be yellow or reversed as in the hotkey menu as shown in https://github.com/ihhub/fheroes2/pull/8079?
First of all, I remember we had similar issue / idea /discussion in the past. Secondly, aesthetically it will look awful. The game shouldn't become a Microsoft Word sort of application. Grouping hot keys into categories (logical work has been done) is a way to keep balance between usability and accessibility.
Another point I might add is that this would have to be left out for users on handheld or touch devices.
I agree that aesthetically it will not look very good to do in the proposed implementation. However, I don't really have an alternative design as of now.
Also if we still want to enhance usability it would be better to show a popup window upon pressing a button. For example, F1 can show a list of hot keys for a particular window where a user currently at.
Also if we still want to enhance usability it would be better to show a popup window upon pressing a button. For example, F1 can show a list of hot keys for a particular window where a user currently at.
That's probably an better solution.
@zenseii This can be closed then.
@Mr-Bajs
That's probably an better solution.
@zenseii This can be closed then.
I suggest to edit the title and description of this issue to reflect @ihhub's suggestion, instead of opening a new one. After all it was suggested as part of the discussion in this issue.