JvanKatwijk
commented
3 years ago the easiest solution would be to make semantics such that if the time specified is before the actual time, it is taken as the time of the following day. Another "solution" would be to allow specification of time beyond 2400 hours (when I was a student it was not uncommon to leave a party atl 27 or 28 hours of the current day)
In the end, however, the scheduling needs to be extebnded. This obviously brings the question what happens if you have a schedule element for say two days later, you switch off your computer the current day and restart the next day: will the schedule be saved or not
Short term solution will be the second option, i.e. allowing specifying an event to occur at e.g. today at 27.30 hours
Op wo 10 nov. 2021 om 22:50 schreef andimik @.***>:
The scheduler only works for the same calender day.
If you want to start a recording in the early morning (let's say 3am) and you want to program it in the evening (let's say 9pm) then the timer immediately starts instead of waiting for 6 hours.
So I fear you need to a day field as well?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/qt-dab/issues/242, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQEN6GZZIWJZREQZMP3ULLSIRANCNFSM5HY7KEGA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
-- Jan van Katwijk
andimik
The scheduler only works for the same calender day.
If you want to start a recording in the early morning (let's say 3am) and you want to program it in the evening (let's say 9pm) then the timer immediately starts instead of waiting for 6 hours.
So I fear you need to add a day field as well?