ShellDetails 1.26 (Content plug-in)

Discuss and announce Total Commander plugins, addons and other useful tools here, both their usage and their development.

Moderators: white, Hacker, petermad, Stefan2

Post Reply
mikeyo
Junior Member
Junior Member
Posts: 3
Joined: 2019-01-10, 19:18 UTC

Re: ShellDetails 1.25 (Content plug-in)

Post by *mikeyo »

Thanks that's better.
User avatar
DrShark
Power Member
Power Member
Posts: 1872
Joined: 2006-11-03, 22:26 UTC
Location: Kyiv, 68/262
Contact:

Re: ShellDetails 1.25 (Content plug-in)

Post by *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.
Donate for Ukraine to help stop Russian invasion!
Ukraine's National Bank special bank account:
UA843000010000000047330992708
User avatar
Lefteous
Power Member
Power Member
Posts: 9535
Joined: 2003-02-09, 01:18 UTC
Location: Germany
Contact:

Re: ShellDetails 1.25 (Content plug-in)

Post by *Lefteous »

2DrShark
The plugin offers different date fields for reading and for writing.
What do you mean by that?
[=shelldetails.Дата съемки.D.M.Y h:m:s]
[=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.
User avatar
DrShark
Power Member
Power Member
Posts: 1872
Joined: 2006-11-03, 22:26 UTC
Location: Kyiv, 68/262
Contact:

Re: ShellDetails 1.25 (Content plug-in)

Post by *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.
Donate for Ukraine to help stop Russian invasion!
Ukraine's National Bank special bank account:
UA843000010000000047330992708
User avatar
Lefteous
Power Member
Power Member
Posts: 9535
Joined: 2003-02-09, 01:18 UTC
Location: Germany
Contact:

Re: ShellDetails 1.25 (Content plug-in)

Post by *Lefteous »

2DrShark
Can you please send me/post the shelldetails.ini entry that contains the mentioned field?
User avatar
DrShark
Power Member
Power Member
Posts: 1872
Joined: 2006-11-03, 22:26 UTC
Location: Kyiv, 68/262
Contact:

Re: ShellDetails 1.25 (Content plug-in)

Post by *DrShark »

Lefteous wrote: 2019-03-04, 07:37 UTCshelldetails.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?
Donate for Ukraine to help stop Russian invasion!
Ukraine's National Bank special bank account:
UA843000010000000047330992708
User avatar
Usher
Power Member
Power Member
Posts: 1675
Joined: 2011-03-11, 10:11 UTC

Re: ShellDetails 1.25 (Content plug-in)

Post by *Usher »

DrShark wrote: 2019-03-03, 16:33 UTC 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…
Last edited by Usher on 2019-04-15, 16:41 UTC, edited 1 time in total.
Andrzej P. Wozniak
Polish subforum moderator
User avatar
DrShark
Power Member
Power Member
Posts: 1872
Joined: 2006-11-03, 22:26 UTC
Location: Kyiv, 68/262
Contact:

Re: ShellDetails 1.25 (Content plug-in)

Post by *DrShark »

Usher wrote: 2019-04-15, 15:29 UTCAs 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.
Donate for Ukraine to help stop Russian invasion!
Ukraine's National Bank special bank account:
UA843000010000000047330992708
User avatar
Usher
Power Member
Power Member
Posts: 1675
Joined: 2011-03-11, 10:11 UTC

Re: ShellDetails 1.25 (Content plug-in)

Post by *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.
Andrzej P. Wozniak
Polish subforum moderator
User avatar
Lefteous
Power Member
Power Member
Posts: 9535
Joined: 2003-02-09, 01:18 UTC
Location: Germany
Contact:

Re: ShellDetails 1.26 (Content plug-in)

Post by *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
Junior Member
Junior Member
Posts: 34
Joined: 2014-11-22, 12:57 UTC

Re: ShellDetails 1.26 (Content plug-in)

Post by *lisabon »

Lefteous,
Current version 1.26
Please compile uwdx.
User avatar
Lefteous
Power Member
Power Member
Posts: 9535
Joined: 2003-02-09, 01:18 UTC
Location: Germany
Contact:

Re: ShellDetails 1.26 (Content plug-in)

Post by *Lefteous »

2lisabon
I remember that there has been a UWDX compilation in the past. I cannot remember why it was needed?
User avatar
LonerD
Senior Member
Senior Member
Posts: 381
Joined: 2010-06-19, 20:18 UTC
Location: Makeyevka, Russia
Contact:

Re: ShellDetails 1.26 (Content plug-in)

Post by *LonerD »

Lefteous wrote: 2019-06-11, 09:51 UTC 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.
"I used to feel guilty in Cambridge that I spent all day playing games, while I was supposed to be doing mathematics. Then, when I discovered surreal numbers, I realized that playing games IS math." John Horton Conway
lisabon
Junior Member
Junior Member
Posts: 34
Joined: 2014-11-22, 12:57 UTC

Re: ShellDetails 1.26 (Content plug-in)

Post by *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.
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48021
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Re: ShellDetails 1.26 (Content plug-in)

Post by *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.
Author of Total Commander
https://www.ghisler.com
Post Reply