https://bugs.kde.org/show_bug.cgi?id=434319
Bug ID: 434319
Summary: Disable "start backup" button while not all conditions
for a backup are met
Product: kbackup
Version: 19.12
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
When starting KBackup and clicking simply "Start Backup", an error message gets
displayed saying nothing was selected for Backup in the console at the bottom.
When starting KBackup and then selecting any file/ folder followed by a click
on "Start Backup", the user simply gets presented with the error notification
in the console saying "target dir \" is not valid" (Also note the single slash
being displayed, which seems incorrect to me…).
I think to be more intuitive it would be better to bind the disabled state of
the "start backup" button to the emptiness of the target dir chooser and the
emptiness of the selection in the file tree, meaning that if any of those is
empty, the button should be disabled.
To show what is missing before starting the backup, the user should somehow be
informed, i.e. by a tool tip on the button or console error messages (as
currently, but statically instead of only when run).
As a result of that the button should be initially disabled when starting the
program and only enabled when these conditions are met.
STEPS TO REPRODUCE
1. Start KBackup
2. Click "Start Backup" Button
a) when no file/ folder has been selected and no target directory has been
set
b) when an file/ folder has been selected but no target directory
c) when only a target directory has been set but no file/ folder has been
selected
3. Observe results and enjoy ;)
OBSERVED RESULT
An error message gets displayed in the console
EXPECTED RESULT
see at the top.
SOFTWARE/OS VERSIONS
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.8.0-44-generic
OS Type: 64-bit
--
You are receiving this mail because:
You are watching all bug changes.
