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
Description: Currently, Playnite opens to the last accessed tab when launched. While this behavior is convenient for frequent users, it would be beneficial to add an option that allows users to set a specific default tab when Playnite starts.
Proposed Features:
Add a setting in the application preferences where users can choose a default tab (e.g., Favorite, All, Most Played, etc.).
Include an option to retain the current behavior of opening the last accessed tab for those who prefer it.
Ensure the default tab setting can be easily accessed and modified within the user interface.
Benefits:
Enhances user experience by allowing personalization based on individual workflows.
Streamlines access to frequently used tabs, improving efficiency for users who have specific tasks in mind when opening the application.
Thank you for considering this enhancement!
Screenshots
No response
The text was updated successfully, but these errors were encountered:
Feature description
Description: Currently, Playnite opens to the last accessed tab when launched. While this behavior is convenient for frequent users, it would be beneficial to add an option that allows users to set a specific default tab when Playnite starts.
Proposed Features:
Add a setting in the application preferences where users can choose a default tab (e.g., Favorite, All, Most Played, etc.).
Include an option to retain the current behavior of opening the last accessed tab for those who prefer it.
Ensure the default tab setting can be easily accessed and modified within the user interface.
Benefits:
Enhances user experience by allowing personalization based on individual workflows.
Streamlines access to frequently used tabs, improving efficiency for users who have specific tasks in mind when opening the application.
Thank you for considering this enhancement!
Screenshots
No response
The text was updated successfully, but these errors were encountered: