Skip to content

SyncControl: fixed bugs to properly jump to an available init/valid time

Closes #392 (closed). There is some weird synchronization behaviour due to some bugs.

  • Bug 1: According to the functionality, we do NOT change the init/valid time when pressing the "select data sources for allowed times and members" when the current time is already one of the available init/valid times. Therefore, the contains check (see changes) must be inverted. We reset the time to the previous one, if the previous one is in the list of available times.
  • Bug 2: Needed to swap the setTimeRange and setDateRange calls. The default times are not 00:00-23:59, therefore setting the date before adapting the times might jump to the nearest possible value, which might be at a different day.
Edited by Christoph Fischer

Merge request reports