You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The expand / collapse labels should also be functional and clickable elements. 10px margin between the words and caret.
We talked about not showing the coordinates on initial page load. But once a user has moved to any coordinate, the value show remain visible to the right of each respective axis label, even when collapsed.
Question: Can we flip the order of slice movement 0-128? Reasoning: The movement seems backwards, especially on the Y axis. I would expect the 10 Ahead to work its way down the slider, since it starts at the top. But it starts at the bottom and works its way up. May be counterintuitive for volunteers.
Style for '10 Ahead' button hover and click
Cube:
The cube overlaps the toolbar at certain smaller browser sizes.
The Figma shows the viewer with the new metatools bar below:
Round the bottom left corner of the cube, as shown.
The histogram functions a lot better after filtering out slices with no data. Nice!
Overall layout:
Add a .5px stroke #A6A7A9 to all sides except the bottom. (Sorry to go back and forth on this!) Dark mode is ok as there are no strokes used.
Question: Anything we can do to keep both the slices and cube horizontally aligned / not transition to stacked alignment for a moderate screen size? Reasoning: A lot of users have a screen size of 1280px, and they won't be able to use the horizontal layout.
Initial thoughts: I like how the Task area starts to become responsive at smaller screen sizes. It gets as narrow as ~250px. Can we do that at larger screen sizes as well?
The text was updated successfully, but these errors were encountered:
Slices:
Cube:
The Figma shows the viewer with the new metatools bar below:

The histogram functions a lot better after filtering out slices with no data. Nice!
Overall layout:
Initial thoughts: I like how the Task area starts to become responsive at smaller screen sizes. It gets as narrow as ~250px. Can we do that at larger screen sizes as well?
The text was updated successfully, but these errors were encountered: