[TC 11.55 RC3] the datetime attributes setting goes wrong

[AntonyD]

And as always - while dealing with another bug, or rather other possibilities to fix it, I came across another bug.

For any file on the disk, open the "Change attributes..." dialog. Add the internal plugin "tc" with the field "writedate" for ex.
through the "More attributes" button on it. Surprisingly Initially the corresponding field is somehow empty?
Although it would be very logical for the value to be fetched automatically. After all, we are ALREADY working with the file.
We ALREADY know the value of the selected field. We just want to change this time now. But no. It doesn't work like that here .
Then the next intuitive step would be to use the ">>" button. So yes, I press it and get a dialog where the value of the datetime
type, which we plan to change through the plugin, is already filled in. So far - so good.
Ok - we agree with this value, Or we slightly adjust it. For the essence of the described bug, this is not critical action at all.
The value is inserted into the corresponding field. And now we AGAIN press the ">>" button and with surprise instead of
the expected the same value, we get this: https://i.ibb.co/9PW4zHC/2025-05-25-112534.png
IF we will press OK - instead of the value which we just saw - finally we will see this: 01.01.9999 00:00:00 in the "tc"
plugin's VALUE field of "writedate".

reproducible on TC x64 but not on TC x86

****************************************************************
What else is unclear about the essence of this bug in principle. Why are these plugin's fields remembered when I click OK?
I didn't use the "F2 Load/Save settings" combo box ability here! So I did NOT want to see these fields the next time
I opened this dialog. But for some reason they show them to me again in this case.

IF I remove these fields, then I can fix this "clearing" only through the OK button, ALTHOUGH - at the same time, the code
is executed NOT only for this logic, but also related to working with other objects on the form of this dialog.
And if I somehow did something there, then instead of the ONE action I wanted - delete all the plugin fields from the scope -
I will also receive the set/clear/change actions for some property/field that was accidentally enabled/disabled by me...

The need for a "+" button on the form is also unclear. It performs the same actions as the "More attributes" button.
So why is the duplication of functionality done? Or are you saying that for some reason I'll install the plugin I need faster?
This is definitely not the case.

[white]

Confirmed.

Seems to be introduced by this change:

18.05.25 Added: When changing file attributes, it's now possible to enter fractions of a second (max 3 digits) in the time field (32/64)

[ghisler(Author)]

1. When you add a new plugin field, it is always empty. Click on one of the "Load from file under cursor" buttons to load the value. I will not change this, sorry.
2. I can confirm the problem with year 1601.

[white]

1. When you add a new plugin field, it is always empty..

It's more nuanced than that. As mentioned before, for boolean values like tc.compressed, tc.encrypted and tc.sparse, the value field will contain "Yes" and not empty (or something like <unspecified>).

[AntonyD]

2ghisler(Author)

1. When you add a new plugin field, it is always empty. Click on one of the "Load from file under cursor" buttons to load the value. I will not change this, sorry.

It has already been very well explained to you above that such behavior is very strange and does not allow the user to understand whether they are being helped or, on the contrary, hindered from performing some correct action using these elements?
EITHER you do NOT fill in anything and in any way in these appearing fields EVERYWHERE,
OR you immediately and automatically enter logically CORRECT values.
Including the case when the LOGICAL value will be, as indicated above, the value "UNDEFINED"

And what about my personal of course judgments under the symbols
***********************************************
Do you have anything to clarify regarding the logic used in the development? We don't understand it yet.

[jiangzhenjerry]

I encounter this timestamp issue where I cannot search by datetime interval: https://imgur.com/a/FM5Atyh

Either it's the same year 1601 bug that invalidates my datetime selection, or it may be due to my Windows 11 (because I just installed the latest Canary build yesterday). Hopefully you guys can double check for me.

[Dalai]

2jiangzhenjerry
Does it work in the latest final (11.51)? If not, it might be due to the wrong date format input; it should match either the short or long date format set in the system.

[white]

I encounter this timestamp issue where I cannot search by datetime interval: https://imgur.com/a/FM5Atyh

Either it's the same year 1601 bug that invalidates my datetime selection, or it may be due to my Windows 11 (because I just installed the latest Canary build yesterday). Hopefully you guys can double check for me.

Confirmed for TC 11.55RC3 64-bit only (other versions work OK). Seems to be related.

[jiangzhenjerry]

2Dalai
Yes it works up to RC2. The date format is matching the system setting.

2white
Thanks for confirming!

[ghisler(Author)]

This should be fixed in RC4, please test it!

Sorry, I forgot to document it in history.txt.

[AntonyD]

2ghisler(Author)
Firstly, the very bug that I showed in the video about the bug in " Unexpected redraw and delayed response to action & unexpected behavior"
has now become very pronounced here. So now and here when you adding a new line with the plugin rule, everything is drawn very badly.

Secondly as to the essence of reported bug - yes, it seems like a fixed one.

Thirdly, all of this: remained uncommented:

****************************************************************
What else is unclear about the essence of this bug in principle. Why are these plugin's fields remembered when I click OK?
I didn't use the "F2 Load/Save settings" combo box ability here! So I did NOT want to see these fields the next time
I opened this dialog. But for some reason they show them to me again in this case.

IF I remove these fields, then I can fix this "clearing" only through the OK button, ALTHOUGH - at the same time, the code
is executed NOT only for this logic, but also related to working with other objects on the form of this dialog.
And if I somehow did something there, then instead of the ONE action I wanted - delete all the plugin fields from the scope -
I will also receive the set/clear/change actions for some property/field that was accidentally enabled/disabled by me...

The need for a "+" button on the form is also unclear. It performs the same actions as the "More attributes" button.
So why is the duplication of functionality done? Or are you saying that for some reason I'll install the plugin I need faster
with help of +?
This is definitely not the case.

[white]

The issue of the wrong date in Change attributes and Search (Advanced tab) tested OK.

[ghisler(Author)]

Thanks for confirming the fix!

Why are these plugin's fields remembered when I click OK?

This is a compromise for repeated searches: The option "Search in plugins" gets unchecked, but the last used fields remain.

The need for a "+" button on the form is also unclear.

The "+" button sets another plugin field as the source for a plugin value, e.g. to copy the EXIF date/time to the last modified date time.

[AntonyD]

The "+" button sets another plugin field as the source for a plugin value, e.g. to copy the EXIF date/time to the last modified date time.

If so, the current bug remains unfixed.
Use this + button and add the value in the field [=tc.writedate]
After that - now press ">>" button and again observer the 1601-year problem.
in its full playback cycle.

P.S.
If in the development logic you meant that the + button should add some special values that
I cannot TYPE character by character in this editing field, then the ">>" button should be completely
disabled for such input because it is only related to the ACTUAL date/time value.

[petermad]

The 1601 year problem is not quite fixed.

To reproduce:
1. Open the Change Attributes dialog:
2. Click on the More attributes button.
3. Choose TC as plugin and Writedate as property.
4. Click on the [+] button and select a plugin.
5. Click on the [>>] button - TC suggest the year 1601.

Or even easier:
4. Write anything but a space in the Value field.
5. Click on the [>>] button - TC suggest the year 1601.