Opened 4 years ago

Closed 4 years ago

Last modified 2 years ago

#259 closed defect (fixed)

Update order problem when changing DateTimeZero while having autoscale off

Reported by: ghorwin Owned by: ghorwin
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 (6)

comment:1 by ghorwin, 4 years ago

Description: modified (diff)

comment:2 by ghorwin, 4 years ago

Diagnosis:

QVariant SeriesLineExtractorModel::axisData(AxisPosition axisPosition, int axisDataRole) const {


    ...
			// special handling if axis date time zero is requested the first time, and is still set to the default value
			QDateTime defaultDateTime(QDate(2000,1,1));
			defaultDateTime.setTimeSpec(Qt::UTC);
			if (axisInformation(axisPosition).m_dateTimeZero == defaultDateTime) {
				// retrieve start year from extractor's first DataIO

....

Die Spezialbehandlung "Wenn DateTimeZero noch Standardwert, dann liefere das Startjahr des Datensatzes zurück" darf nicht angewendet werden, wenn bereits einmal das DateTimeZero verändert wurde und entsprechend die Minimum/Maximum-Werte angepasst wurden.

Lösungsideen:

  • DateTimeZero mit ungültigem Wert initialisieren und entsprechende Fallbehandlung durchführen

comment:3 by ghorwin, 4 years ago

Resolution: fixed
Status: newclosed

comment:4 by ghorwin, 4 years ago

Owner: set to ghorwin

In 1087/SciChart:

Fixed #259 (when changing DateTimeZero to 01.01.2000, Min/Max-Values weren't updated correctly).

comment:5 by ghorwin, 4 years ago

In 1253/PostProcPart:

Fixed #259 (when changing DateTimeZero to 01.01.2000, Min/Max-Values weren't updated correctly).

comment:6 by ghorwin, 2 years ago

Milestone: 2.2.42.3.0

Milestone renamed

Note: See TracTickets for help on using tickets.