Opened 4 years ago

Last modified 2 years ago

#259 closed defect

Update order problem when changing DateTimeZero while having autoscale off — at Version 1

Reported by: ghorwin Owned by:
Priority: critical Milestone: 2.3.0
Version: 2.2.x Keywords:
Cc: Operating System: all

Description (last modified by ghorwin)

Steps to reproduce:

  • enable DateTime
  • disable autoscale 
DateTimeZero = 1.1.2001
Min = 1.1.2001
Max = 1.1.2002
  • change DateTimeZero to 1.1.2002

Min/Max times are adjusted correctly

  • change DateTimeZero to 1.1.2000 (the default value)

MinMax times are kept and thus become invalid when DateTimeZero is changed next

Change History (1)

comment:1 by ghorwin, 4 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.