Remove item selection from the item request slot editor
Posted: Wed Mar 23, 2022 3:18 am
Hi,
TRTRLT; Don't show items when changing already set item requests amounts (Not if it's a new, blank request slot).
When changing the amount of items being requested of a currently selected item request slot, the popup screen contains the item selection screen. This moves the slider and Confirm button away from the button that gets you into that dialogue. This goes against good UI design principals, specifically where you should minimise the distance you make your users move their mouse.
A better design would not show the item selection UI component. Without the item selection component you have to move your mouse far less. It also means that you end up having your cursor closer to the possible next item that you're going to change as it's extremely common to change multiple item requests at once, eg requesting items for a reactor or similar rare builds.
I also put the currently selected item to give the user good feedback that they clicked the correct item. This could be used to give access to the item selection component if required, but I believe that clearing an item selection when changing the type of item being requested might already be the common workflow.
Please be aware that the screenshots show an exaggerated example without the category tabs, but the UX design principal still applies even if the categories are enable.
TRTRLT; Don't show items when changing already set item requests amounts (Not if it's a new, blank request slot).
When changing the amount of items being requested of a currently selected item request slot, the popup screen contains the item selection screen. This moves the slider and Confirm button away from the button that gets you into that dialogue. This goes against good UI design principals, specifically where you should minimise the distance you make your users move their mouse.
A better design would not show the item selection UI component. Without the item selection component you have to move your mouse far less. It also means that you end up having your cursor closer to the possible next item that you're going to change as it's extremely common to change multiple item requests at once, eg requesting items for a reactor or similar rare builds.
I also put the currently selected item to give the user good feedback that they clicked the correct item. This could be used to give access to the item selection component if required, but I believe that clearing an item selection when changing the type of item being requested might already be the common workflow.
Please be aware that the screenshots show an exaggerated example without the category tabs, but the UX design principal still applies even if the categories are enable.