[TC 11.55 RC3] the datetime attributes setting goes wrong

[ghisler(Author)]

The 1601 year problem is not quite fixed.

That's NOT the same problem! The problem found by the thread starter was caused by addition of millisecond support. Missing milliseconds in an otherwise valid date resulted in the year 1601 bug.

What you describe now has happened also in TC 11.51 and older: When the field contains an INVALID date, the date picker shows the year 1601.

[petermad]

Well, it applies to the topic title: "the datetime attributes setting goes wrong" An is mentioned by the topic starter here: https://www.ghisler.ch/board/viewtopic.php?p=472295#p472295

[AntonyD]

Code: Select all

27.05.25 Fixed: Files - Change attributes: Date/time picker showed invalid year 1601 when a plugin field contained invalid data like random text -> show current date and time (32/64)

I saw this I tried to use it. and yes. Exactly as it was described it does work. BUT ....
it seems to me that if I add true gibberish to this field, then yes, your approach is logical.
but! if this field contains some value with a date, but simply formatted as the value
of some field from some plugin, then isn't it possible to GET this very value and display it?
That is, I literally wrote the words "[=tc.writedate]" in an editbox and then clicked ">>" - isn't it
possible to first turn "[=tc.writedate]" into the real date "27.05.2025 14:08:21", which is stored in
this literal equivalent. And after that, display this real date in the date selection dialog that appears?

[petermad]

27.05.25 Fixed: Files - Change attributes: Date/time picker showed invalid year 1601 when a plugin field contained invalid data like random text -> show current date and time (32/64)

Confirmed fixed in TC 11.55rc5

[ghisler(Author)]

2petermad
Thanks for confirming the fix!

2AntonyD
Reading data from potential plugin fields would be a nice new feature. However, I don't want to add it at this time, because it could cause a lot of new bugs which would make the beta test longer. Maybe in a later version.

Moderator message from: ghisler(Author) » 2025-06-05, 07:22 UTC

Moved to fixed bugs