The problem is NOT with validity, but with meaning. For me current behavior seems inconsistent.
For attribs empty field means "reset value", and "unchanged" is for grayed-out field - no matter if it is the initial state or if it's changed back to grayed-out.
There are more values enabled for date/time fields, but the meaning should be similar:
- Placeholder for "unchanged" (with possible extensions for partial placeholder, f.e. change only year using 1999-mm-dd value). You can additionally gray-out placeholder or use grayed-out empy field for this purpose.
- Empty field for reset. The question is: what value should be use here - current date/time stamp or maybe 1980-01-01 and 00:00:00? There is already button for current timestamp, and TC already uses empty part of time to reset it to zero, so why not extend this behavior for dates also? That way "1999" will mean 1999-01-01, empy time will be "00:00:00" and it will be consistent with other settings.
Unusual behavior in Change Attributes dialog
Moderators: white, Hacker, petermad, Stefan2
- ghisler(Author)
- Site Admin
- Posts: 48083
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
For timestamps, empty fields or placeholder mean "unchanged". This is documented in the help.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
Indeed, you are right - so both 32-bit and 64-bit TC work in a consistent way.petermad wrote:2MarcinW
Try and restart your 64bit TC, then the placeholders are shown - but once the fields has been blanked (for example after faulty input) it stays blank until TC restarts.
So, as for me, this thread could be moved to "Fixed Bugs".
Regards