- Issue created by @Grimreaper
- Status changed to Postponed: needs info
9 months ago 6:49pm 22 December 2023 - π¬π§United Kingdom longwave UK
Isn't that just because that time doesn't exist? Europe moves to daylight savings time between those hours and so the clock jumps from 01:59:59 to 03:00:00.
- Status changed to Closed: works as designed
9 months ago 8:54pm 22 December 2023 - π¦πΊAustralia larowlan π¦πΊπ.au GMT+10
Sounds like this works as designed
- π«π·France Grimreaper France π«π·
Hi,
Thanks for the quick feedback.
First time this happens to me on a project. I have totally forgotten this time move...
The probability to have an event which ends precisely this day at this time...Sorry for the noise... Date and time, always a nightmare.
I just wonder in the opposite way (when going back of one hour), when for example entering this in the datetime widget 2024/10/27 02:30:00, is it designating the time before the time move or after the time move? How to be able to designate one or the other? Or is it existing in timestamp only but in datetime, this hour does not exist too?