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
Currently, clicking the refresh icon in the lower right of a file browser in the left pane of LMMS will cause all of its folders to be collapsed.
Ideal behavior, in my mind, is to preserve the collapsed/expanded state of all folders that existed before the refresh and have only the newly created folders default to being collapsed. Similarly, if a file/folder was selected before the refresh, it should also be selected after the refresh, if it still exists, though that's a minor difference.
The text was updated successfully, but these errors were encountered:
I have already once made a topic around this, but it was dismissed. I have to chime in on this one, because the current behavior is a real anointment (imo)
Considder why the refresh is used:
The user open a folder, where he expect to find a particular preset
User enters a search-token
The search gives no usable result
The reason must be that the token was wrong OR the folder was wrong
so:
1 Token is wrong
If the user now press refresh the token remains, but the browser is empty -eg no further search possible
Current behavior is useless, and he has to manually delete the erroneous token
2 Folder is wrong
If the user now press refresh the browser is empty. There is no folder-tree to access -eg no further search possible
Current behavior is useless -again
In which circumstance is the current behavior of refresh useful /make sense?
Currently, clicking the refresh icon in the lower right of a file browser in the left pane of LMMS will cause all of its folders to be collapsed.
Ideal behavior, in my mind, is to preserve the collapsed/expanded state of all folders that existed before the refresh and have only the newly created folders default to being collapsed. Similarly, if a file/folder was selected before the refresh, it should also be selected after the refresh, if it still exists, though that's a minor difference.
The text was updated successfully, but these errors were encountered: