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
On changing between sample and feature metadata barplots, the "Default length" / "Length" values should be updated to what they were in the previous tab.
On enabling / disabling length scaling for feature metadata barplots, the "Maximum length" and "Default length" values should be updated to match each other.
These changes might be frustrating if a user purposefully wants a sample metadata barplot with a different length than a feature metadata barplot or whatever, but for most users this should smooth out the UI.
I just noticed something a bit off with the bar scaling, maybe worth fixing here? When you click on the scale checkbox and you have a length different to 100 (the default), the maximum length is set by default to 100. I think this should by default be the maximum length so that bars don't shrink out of the blue. See this animated gif:
That's a really good point, and I agree that the UI for this is a bit confusing. Part of the challenge here is that, if the user has already done some length-scaling stuff for a layer, I'm not sure we want to mess with that when the user switches back to non-length-scaling -- do you think an acceptable compromise would be setting the "max length" for scaling to the default length the first time the "length scaling" checkbox is checked? Or maybe we should just update it every time.
I guess in the same vein we should definitely synchronize the default lengths between feature and sample metadata barplots --
The text was updated successfully, but these errors were encountered:
Desired changes
These changes might be frustrating if a user purposefully wants a sample metadata barplot with a different length than a feature metadata barplot or whatever, but for most users this should smooth out the UI.
Discussion
From @ElDeveloper, in #357:
Another reply in #357:
The text was updated successfully, but these errors were encountered: