[qt] reorder per-game context menu #3131
No reviewers
Labels
No labels
android
audio
bug
ci
cmake
confirmed
core
desktop
duplicate
enhancement
frontend
fw
git
graphics
loader
nv gpu
ui
vulkan
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
eden-emu/eden!3131
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "reorder-menu-game-per-config"
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?
reorders the context menu based on what the user is likely to choose
also does a few renamed so the names are sorted (like View on GameDB and all that)
Signed-off-by: lizzie lizzie@eden-emu.dev
This new ordering is significantly less intuitive and also changes things around for no apparent reason. Why?
@crueter wrote in #3131 (comment):
I based the reordering based on what youre likely to use as a user
Most users just want to see the mods folder/save data folder; rarely they ever go into the pipeline cache folder
Additionally, most users can't read too many words in the "remove" submenu
My idea is that there is less items per submenu, they get more "distributed" instead of stashing a bunch of things into the "remove" subemnu
Intuitively it does make sense since most things are where they are supposed to (for example pipeline cache).
Again this is mostly based on "user will use this X more commonly than Y"; and knowing users its probably good to show things mroe concisely
Users for example are way less likely to use the copy title id option as opposed to "open mod/save" option, hence, its put at the bottom
The reordering is based on my subjective perception for what the user would prioritize at any given moment (sure when a user is setting up eden after using ryujinx they may like the link to ryujinx option to be at the top, but most users do not use that as often as "open mod directory")
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.