Invalid date (Info panel > Properties tab)

[RedElbows]

Yesterday, I updated from version 18.10.0000 to 18.20.0000, then a short time later from version 18.20.0000 to 18.20.0100.

"Show Milliseconds" is now displaying to only three decimal places, whereas before it was displaying to seven decimal places. This, in turn, is giving me an "Invalid date" error when I attempt to modify the timestamp, and I think it's being caused by the way the milliseconds are being displayed… but I don't know for certain.

Is this a bug or a configuration issue??

[admin]

Confirmed and fixed (next beta), thanks!

[RedElbows]

That's awesome… thanks!! However, timestamps in the properties tab are still only displaying milliseconds to three decimal places (v.18.20.0102). I've downgraded to v.18.10.0100 (for now) and milliseconds are again displaying seven decimal places.

[admin]

That's awesome… thanks!! However, timestamps in the properties tab are still only displaying milliseconds to three decimal places (v.18.20.0102). I've downgraded to v.18.10.0100 (for now) and milliseconds are again displaying seven decimal places.

Yes, I recently made it that everywhere the same number of decimal places is displayed. (see viewtopic.php?p=151309#p151309)

Ha, but now I remember why I had always 7 digits in the properties tab! I wanted to deliver maximum precision where screen space does not matter. I will change it back. (Hope you understand, Marco)

BTW, you can change the number of decimal places using this (officially undocumented) script command:

Code: Select all

syntax: msecs [show], [numberofdecimalplaces], [cropzeros]

Examples:
msecs;   // toggle
msecs 0; // turn on
msecs 1; // turn off
msecs(1, 0); // turn on, set to factory default (3 places)
msecs(1, 3); // turn on, set to 3 places (factory default)
msecs(1, 7); // turn on, set to 7 places (maximum
msecs(1, 4, 1);  // turn on, set to 4 places, crop trailing zeros