UI Post-Refactor Revisions [AARD-2002]#1268
Conversation
PepperLola
left a comment
There was a problem hiding this comment.
Looks good overall but I noticed a couple things.
- I think the match mode config panel items could use some padding
- I'm not sure whether it makes more sense to close configure/spawn when the other is opened or to block the opening, because the user could be in the middle of configuring something and then opening spawn panel would cancel all their changes
- When dragging a slider in the settings modal all the way to the left or right the handle gets cut off, and on the right side it overflows and causes there to be a horizontal scroll bar
- I'm not sure how to address this, but I think the empty accordions in the spawn panel look a bit weird when expanded.
Maybe just a message that is like "No Saved Assets" / "No Assets Found" rather than leaving it empty |
I think configure closing spawn is fine, but if configure is editing something (not just open) then spawn should show a warning |
| boxShadow: "0 4px 12px rgba(0,0,0,0.28), 0 2px 6px rgba(0,0,0,0.18)", | ||
| }, | ||
| }, | ||
| }, |
There was a problem hiding this comment.
What do you think about adding something like this? This blurs the background if you have a modal open which I think is better.
| }, | |
| }, | |
| MuiBackdrop: { | |
| styleOverrides: { | |
| root: { | |
| backgroundColor: "rgba(0, 0, 0, 0.5)", | |
| backdropFilter: "blur(2px)", | |
| }, | |
| }, | |
| }, |
There was a problem hiding this comment.
- Pressing the plus button on the configure asset panel doesn't open the spawn assets panel anymore
- There is no feedback for why the config panel doesn't open when the spawn asset panel is open. I think it makes more sense to make the newly-opened one replace the other, unless you're editing a configuration, at which point it should show a warning toast
- Panels can still be too tall
- The configure panel for inputs seems to skip to a specific scheme instead of showing the list (and there are no breadcrums)
- The APS import folder doesn't have any text when empty
- If only parts of a panel are going to be draggable, there should be a visible distinction (maybe a handle like this)
PepperLola
left a comment
There was a problem hiding this comment.
- I would like the APS spinner to be either the same height as the text (ideal) or centered vertically.
- The default height of the initial config panel makes the accept/cancel buttons overflow. Maybe a worthwhile change would be making the modal/panel content scrollable but keeping the buttons visible (and the title as well)
- If it's not too difficult it would be nice to have the slider labels match the other ones (in size + alignment/indentation); right now they look a bit out of place
- This toggle group should be centered horizontally like in the spawn assets panel, and the buttons shouldn't touch the bottom of the panel (latter would be fixed by always showing accept/cancel)
rutmanz
left a comment
There was a problem hiding this comment.
Approving because you've addressed my previous review and everybody else has caught my remaining feedback
|
How hard would it be for you to go through and increase the maxHeight of all panels to something closer to 85vh? I think that would be nicer. |
PepperLola
left a comment
There was a problem hiding this comment.
- Can the panel title and button background be the same color as the content? I prefer the lighter background color between the two of them
- Can we make the input buttons say "..." when you click them rather than "PRESS ANYTHING"?
PepperLola
left a comment
There was a problem hiding this comment.
The requested changes were not addressed.
- updated main hud with new buttons, made button group - made modal colors consistent with panel - switched to using tabs instead of toggle button groups - fixed aps reload button disappearing on import panel reopen
00c3cfb to
399e93e
Compare








Task
AARD-2002
This task involved collecting bugs relevant to the UI refactor from you guys and writing fixes for each one.
Task list:
Draggable region distinctionSymptom
The UI refactor was a large code edit and brought various visual bugs with it. The UI was, in most cases, fully usable, but the styling wasn't production-ready.
Solution
Fixing individual issues over time by collecting purposeful data.
Verification
Look good? Yay! Look bad? Aw man :(
Before merging, ensure the following criteria are met: