t1m0thyj / WinDynamicDesktop

Port of macOS Mojave Dynamic Desktop feature to Windows

Home Page:https://windd.info

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

new configuring schedule bug

gulk1 opened this issue · comments

  • WDD Version: 5.4.2
  • OS Version: W10 LTSC 21H2

Steps to Reproduce:

  1. Start the program since daylight savings today.
  2. Get an error.
  3. Try to configure schedule via location name or window location

Are you using the Microsoft Store version of WDD?: No

Error:
[2024-04-01 00:21:59.127] System.ArgumentException: The supplied DateTime represents an invalid time. For example, when the clock is adjusted forward, any time in the period that is skipped is invalid. (Parameter 'dateTime') at System.TimeZoneInfo.ConvertTime(DateTime dateTime, TimeZoneInfo sourceTimeZone, TimeZoneInfo destinationTimeZone, TimeZoneInfoOptions flags, CachedData cachedData) at System.TimeZoneInfo.ConvertTime(DateTime dateTime, TimeZoneInfo destinationTimeZone) at WinDynamicDesktop.SunriseSunsetService.GetSunPhases(DateTime date, Double latitude, Double longitude) at WinDynamicDesktop.SunriseSunsetService.GetSolarData(DateTime date) at WinDynamicDesktop.SolarScheduler.CalcNextUpdateTime(SolarData data, DisplayEvent e) at WinDynamicDesktop.EventScheduler.Run(Boolean forceImageUpdate, DisplayEvent overrideEvent) at WinDynamicDesktop.ScheduleDialog.HandleScheduleChange() at WinDynamicDesktop.ScheduleDialog.okButton_Click(Object sender, EventArgs e) at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_0(Object state) at InvokeStub_SendOrPostCallback.Invoke(Object, Span1)
at System.Reflection.MethodBaseInvoker.InvokeWithOneArg(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)`

This error only happens during the 0100-0200 hour on the day after the time changes. I've fixed it for next year in 0903490 😀

This error only happens during the 0100-0200 hour on the day after the time changes. I've fixed it for next year in 0903490 😀

aha.. I was wondering why it fixed itself a day later.

Fixed in WinDD 5.5.0