Robin
As a user, one thing I always wonder (and have to check on) when using anyone’s “time tools” is whether or not it’s a 1-time operation or whether it will have me installing an ntp daemon, etc. Again, maybe it’s only me, but a descriptive line either way would help.
Hi @Grindstone, many thanks for checking the update. I’ve noticed that also, and already changed yesterday the wording so it is clear now that one entry is used for constantly keeping the time synced, which is done by the openntpd service (aka: daemon), and the other entry merely requests a single ntp package from a time server, which is processed completely inside the backend script internally, no ntp system service is started nor needs to be installed for that. Sorry, this fix wasn’t at git still.
New version of fetch_time-and_date with the updated wording and some additional fixes in workflow ergonomy is already at my git now (follow link in opening posting).
Please let me know whether the wording sounds natural now to native English speakers, or whether something can be further improved.
Additional further improvement planned. There is an option to add tooltip hints in yad lists for each entry, which I’ll implement.
Btw, I noticed some trouble with the manual time setting routines we have used for years. Some of them I’ve already fixed now (e.g. not changing the time when aborting, and not asking for minutes if user clicks abort in hours already), but still changing the date sets off the seconds to zero, even when they are actually e.g. 59, so the clock is wrong by a minute after changing the date! Bad bug, needs fixing. Will see what I can do.
Windows is like a submarine. Open a window and serious problems will start.