ShellDetails 1.26 (Content plug-in)

[mikeyo]

Thanks that's better.

[DrShark]

The plugin offers different date fields for reading and for writing.
For reading, e.g. in Custom Columns, it's possible to choose the field for photo shooting date in format:
[=shelldetails.Дата съемки.D.M.Y h:m:s]
For writing, e.g. in Change Attributes... to write that data to a tc comment, it's possible to choose only a similar field:
[=shelldetails.Дата съемки.D.M.Y h.m.s]
I don't know whether it's fault of a ShellDetails plugin, Explorer shell, or TC which filters data for its tc.comment field, but it would be nice to have both above fields available for reading and for writing.

[Lefteous]

2DrShark

The plugin offers different date fields for reading and for writing.

What do you mean by that?

[=shelldetails.Дата съемки.D.M.Y hs]

[=shelldetails.Дата съемки.D.M.Y h.m.s]

The field definition looks identical to me but maybe my bad understanding of Cyrillic letters made me oversee an important detail.

[DrShark]

The difference is that colons (:) are used for time if to choose the ShellDetails additional date/time format in Custom Columns configuration (there with [+] button open "Choose plugin property" dialog, in it on Properties side find a field with name with should mean a capture date, expand it with "+" to select the date format - I see there one with colon, D.M.Y h:m:s), and dots (.) instead of colons are used for time in the same "Choose plugin property" dialog when it opened from Change Attribute... dialog. Even if I write manually a property with colon ([=shelldetails.Дата съемки.D.M.Y h:m:s]) in Change Attributes, dots appear instead of colon in a file comment anyway.

[Lefteous]

2DrShark
Can you please send me/post the shelldetails.ini entry that contains the mentioned field?

[DrShark]

shelldetails.ini entry that contains the mentioned field?

Code: Select all

[{14B81DA1-0135-4D31-96D9-6CBFC9671A99}36867]
Caption=Дата съемки
UseDefault=1
State=131747

Do you need additional screenshots?

[Usher]

The difference is that colons (:) are used for time (...)
and dots (.) instead of colons are used for time

As you know, colon is NOT allowed in file/directory names in Windows. Maybe that's the reason of writing limits. I didn't read the whole topic, just guessing…

[DrShark]

As you know, colon is NOT allowed in file/directory names in Windows. Maybe that's the reason of writing[\b] limits.

As I wrote here, I don't know where a limitation comes from when a ShellDetails plugin field is used as a source for tc.comment field, but if to type colon directly, TC will write it to a comment correctly.

[Usher]

It was just a helpful hint from the programmer's point of view. Using other words - it may be a matter of improper expression/function/condition reusing, possibly some mistake during copy-paste operation.
You know the plug-in better, so you probably know better, if there may be similar points of failure in other plug-in settings.

[Lefteous]

Current version 1.26
A new version is ready for download. The new version adds support for a formerly unsupported numeric field type. The plugin is now open source (see included LICENSE file). The project can be found on GitHub.

The complete list of changes can be viewed online.

Plugin page: Download, description und documentation
totalcmd.net

[lisabon]

Lefteous,

Current version 1.26

Please compile uwdx.

[Lefteous]

2lisabon
I remember that there has been a UWDX compilation in the past. I cannot remember why it was needed?

[LonerD]

I remember that there has been a UWDX compilation in the past. I cannot remember why it was needed?

For Unicode support.
Now TC have native Unicode, and you can make single unicode wdx-file.

[lisabon]

2Lefteous
A wish from another forum (ru-board) by user CaptainFlint:

need to create and export ContentGetValue () with any content (say, "return ft_notsupported;"), then the WDX file will normally be picked up by Total.

[ghisler(Author)]

uwdx is only needed if you want to compile a separate Unicode and ANSI version of the DLL. If you can combine the two into one file, you can also create just a wdx file. However, the ANSI functions must be present for TC to recognize the file as a valid plugin.