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 primary use case is admittedly superfluous, but it can improve direct usability for the end-user.
When you open the app and are greeted by the Subscriptions pane, or navigate to the Creators pane, your creators list is sorted by Watchtime Descending as the default sorting method. While this can work for the short creator taskbar at the top of the Subscriptions pane, it is jarring for the Creators display, as opening a complete list of something usually means that you want to search for something out of the entire pool rather than immediately search for your 10th most-watched creator. Currently, there is no way to change the default sorting method for the Creators pane.
Proposal
Implement a setting variable linked to the Creators pane list which sets the default sorting method, utilizing the current default value if desired.
References
No response
The text was updated successfully, but these errors were encountered:
Use Cases
The primary use case is admittedly superfluous, but it can improve direct usability for the end-user.
When you open the app and are greeted by the Subscriptions pane, or navigate to the Creators pane, your creators list is sorted by Watchtime Descending as the default sorting method. While this can work for the short creator taskbar at the top of the Subscriptions pane, it is jarring for the Creators display, as opening a complete list of something usually means that you want to search for something out of the entire pool rather than immediately search for your 10th most-watched creator. Currently, there is no way to change the default sorting method for the Creators pane.
Proposal
Implement a setting variable linked to the Creators pane list which sets the default sorting method, utilizing the current default value if desired.
References
No response
The text was updated successfully, but these errors were encountered: