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 procedure in the UI for changing the datatype is different depending on whether a conversion is possible for the dataset.
E.g. For some datasets you have to click on the "Convert" tab, and for datasets without conversions available the tab is named "Datatypes" tab. To me it would make more sense to always have this tab be "Datatypes", and letting that tab have a convert option or not depending on the datatype.
e.g. our FAQ for changing datatype says to click on the convert tab, but sometimes it is the Datatypes tab, and I think it would be easier for users to recognize if it's always the same name.
The text was updated successfully, but these errors were encountered:
xref #5768, we have the space for the tabs, we could un-unify them. Or at least give it a unified title/icon, whether showing just datatype change, or datatype change + convert
I don't think we want to separate them again -- the problem before was that it was confusing to users why we had two tabs next to one another that did (at face value) similar things. I think we should probably just make the tab title static and more appropriate reflecting "Things related to the datatype here", as in the original issue.
The procedure in the UI for changing the datatype is different depending on whether a conversion is possible for the dataset.
E.g. For some datasets you have to click on the "Convert" tab, and for datasets without conversions available the tab is named "Datatypes" tab. To me it would make more sense to always have this tab be "Datatypes", and letting that tab have a convert option or not depending on the datatype.
e.g. our FAQ for changing datatype says to click on the convert tab, but sometimes it is the Datatypes tab, and I think it would be easier for users to recognize if it's always the same name.
The text was updated successfully, but these errors were encountered: