UX improvements to settings - unsaved reminder, save button placement, paths validation #438
Open
1 task done
Labels
enhancement
New feature or request
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:
No active news servers available
I install nzbget a lot, and this default my.newsserver is just killing me, it's there but you kind of forget about it sometimes. Competitors have a wizard to add it upon installation, some good software shows a red exclamation mark if something critical is not configured.
If there are no news servers configured, and default my.newsserver isn't considered, please show a red
[1]
near the Settings tab, and News Servers under Settings (so it's clear what's the warning about).Extra information
No response
The text was updated successfully, but these errors were encountered: