gm10 wrote: ↑
Sat Aug 24, 2019 8:30 am
BG405 wrote: ↑
Wed Aug 21, 2019 12:23 pm
Next release of my fork of Update Manager will have the second option here:
Question to both of you, however: Would you expect the first option to work independently of the second one, i.e. to override it? Or would you expect them to work such that the first option would hide the Update Manager window automatically only after the installation popup window has been hidden? I'm a little unsure right now so I thought I'd just ask since it's your workflow more than mine. I will, of course, adjust the wording of the options depending on the way I end up going with to make this clear to the user.
Also I noticed that the "Hide" option does not apply to kernel installations, should probably be applied to that as well.
@gm10 In the python code of mintUpdate.py, just check if the user has opted in to "automatic updates"
and if so, just let the update window close
as it does now. Otherwise, leave it open with both the close button and the checkbox for "always close" always visible
so the user can always have the option in plain sight
. I believe the checkbox setting for "always close" is/was the same setting that belongs to Synaptic Package Manager
to "close when installation is complete". Again, this setting would be ignored if "automatic updates" is selected in the Update Manager.
This would achieve the apparent desire for "Automatic Updates" to just work in the background without interrupting the user. I suspect this was intended for less technical user. However, developers, etc. tend to keep track of updates to many different items like Samba, kernels, and other system related services/technical details that relate to their jobs, or interests, because upstream changes and regressions have often broken system components like drive mounts, networking, mouse accuracy, monitor support and management, etc. in the recent and not so recent past.
Benefits of this solution are:
Automatic Updates occur without interrupting the user.
Fewer configurable options to maintain.
Re-use of existing configuration options that reflect the users preferences.
Reduction of code, keeps code simpler which promotes reliability and reduces brittleness, avoids possible technical debt.
If you'd like me to put this into a feature request on Github, just let me know.