-
-
Notifications
You must be signed in to change notification settings - Fork 340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve UX of street lighting overlay (direct display of options instead of "select" button) #5539
Comments
I did do a brief search for street lighting and didn't find anything. Shall I close this issue? |
I would suggest to change the title to without select button. The idea is to get rid of it |
Yes, it should be closed as duplicate. Thanks for triage @matkoniecz , it is fine to close duplicates. Note that you have the button to the lower left which lets you select the last answer you provided. |
#4622 was closed because "This is the default interface for overlays and I want to keep it that way for consistency." However now we have a row of 6 option buttons below the "select" button in the building overlay. If the building overlay interface is also used for the lighting overlay, it would only show 4 buttons because there are only 4 answer options. For consistency the "select" button could still be shown but it won't be needed any more :) |
Hard to say for me. But if issue is created and it requests the same as already closed issue - then it should link to each of them and explain why it is not duplicate of each. |
Use case
When answering the street lighting quest, there is currently one dropdown with a proposed lighting type.
If the currently selected answer is not the right one, two clicks are necessary to change it before clicking okay.
Proposed Solution
The dropdown could be replaced with the four buttons being directly layed out from left to right (similar to the house level/roof combinations in the house level quest).
That way, answering would be much easier
The text was updated successfully, but these errors were encountered: