NZBGet's UI is quite unfriendly to troubleshooting and new users, this issue is mostly based on community feedback from github and discord. NZBGet should stay fast and clean, however there's no harm if we improve user experience, at least in small steps.
Proposed changes
Unsaved reminder
Currently if you make changes to settings, mostly PATHS configurations and NEWS SERVERS changes - the fact the changes need to be saved isn't communicated to the user, even through tabs cycling (within settings), and you are only reminded if you are leaving Settings. Which is not great if you are working on configurations, and you forgot to click "SAVE" because the button is not visible.
So if there are unsaved changes:
Show "unsaved" near the modified field
Move the save button so it's more visible
Suggest changes if user switched between settings tabs too
Save button positioning
Related to previous request - if there are unsaved changes, a more visible save button is a must. Either move it up permanently, or duplicate it at the top on unsaved changes.
Paths validation
NZBGet can be a bit confusing on paths, especially if download and intermediary paths are on network storage, on removable media. On various platforms the slashes in paths are different, and sometimes you can't easily test it.
When user makes changes to the path, add a button/icon/function to validate it, results can be:
Is there already an issue for this request?
Platform
All
Describe the enhancement you'd like
Purpose
NZBGet's UI is quite unfriendly to troubleshooting and new users, this issue is mostly based on community feedback from github and discord. NZBGet should stay fast and clean, however there's no harm if we improve user experience, at least in small steps.
Proposed changes
Unsaved reminder
Currently if you make changes to settings, mostly PATHS configurations and NEWS SERVERS changes - the fact the changes need to be saved isn't communicated to the user, even through tabs cycling (within settings), and you are only reminded if you are leaving Settings. Which is not great if you are working on configurations, and you forgot to click "SAVE" because the button is not visible.
So if there are unsaved changes:
Save button positioning
Related to previous request - if there are unsaved changes, a more visible save button is a must. Either move it up permanently, or duplicate it at the top on unsaved changes.
Paths validation
NZBGet can be a bit confusing on paths, especially if download and intermediary paths are on network storage, on removable media. On various platforms the slashes in paths are different, and sometimes you can't easily test it.
When user makes changes to the path, add a button/icon/function to validate it, results can be:
Extra information
No response