ShellDetails 1.26 (Content plug-in)

[Lefteous]

However, the ANSI functions must be present for TC to recognize the file as a valid plugin.

ShellDetails 1.26 doesn't export the ANSI version of ContentGetValue, but the plugin is still recognized as a valid plugin in the 64-Bit version of Total Commander. I think this is because there has never been a 64 bit version of Windows that doesn't support Unicode.
I will change this in future versions to exporting a dummy function.

[ghisler(Author)]

The 64-bit version may be Unicode only too, that's why there is no uwdx64 extension. Total Commander 64-bit will use ANSI functions only if there are no Unicode functions available.

[nn1k3]

"This is not a valid plugin."
Sorry, but I cannot install ShellDetails v1.26 with 32-bit TC.
This is not urgent because I am quite happy with v1.25.

[Dalai]

2nn1k3
Do you use Windows XP? Seems like ShellDetails 1.26 won't work on XP and older anymore. That's because its PE Header says that it requires Windows 6.0 (Vista).

Regards
Dalai

[Usher]

2nn1k3Do you use Windows XP? Seems like ShellDetails 1.26 won't work on XP and older anymore. That's because its PE Header says that it requires Windows 6.0 (Vista).

It's typical for default MSVC config. It's been explained here:
https://www.ghisler.ch/board/viewtopic.php?f=6&t=54221&p=360529&hilit=%2Fsubsystem#p360529

[nn1k3]

2 Dalai from nn1k3:
regarding "this is not a valid plugin"
My operating system is Windows 10 64-bit. I use Total Commander 9.22a 32-bit. ShellDetails v1.25 has worked well for me.

[Dalai]

I can confirm the issue (tested on Windows 7 and 1809). However, it can be worked around by renaming ShellDetails.wdx to ShellDetails.uwdx. My guess is that since ShellDetails.wdx only exports the Unicode variant of ContentGetValue function (ContentGetValueW) but not the ANSI function ContentGetValue itself, it's not considered a valid plugin by TC because ContentGetValue function must be implemented according to the plugin writer guide.

Regards
Dalai

[nn1k3]

2 Dalai from nnik3:
Regarding "this is not a valid plugin", thank you for pointing out that uwdx is relevant.
I see now that the zip file for shelldetails v1.26 contains one less file than the zip file for v1.25 ― it is missing ShellDetails.uwdx.
Thus if I install v1.26 OVER v1.25 all is well, but if I were to first uninstall and delete the folder for v1.25, then and only then do I get the error message. So I am all set now, thanks to you.

2 Lefteous from nn1k3:
I am grateful for your plugins, and humbly ask that you consider whether the zip file for shelldetails v1.26 should include a uwdx file.

[Dalai]

Thus if I install v1.26 OVER v1.25 all is well [...]

No, not really because TC prefers .uwdx files and uses them if present. In other words: TC would use the older plugin version when doing this. That's why I suggested to rename the new plugin file.

Regards
Dalai

[nn1k3]

Dalai wrote: That's why I suggested to rename the new plugin file.

Yes, that works well. It took me a while to see how to implement your workaround, so let me try to outline the steps.

I found that I could not install ShellDetails v1.26 unless a file named "ShellDetails.uwdx" is already present in the ShellDetails plugin destination folder.

Ideally, Lefteous would include that uwdx file with his zip file. But until then, these steps worked for me:
1. Uninstall v1.25 and delete or rename the ShellDetails plugin folder.
2. Download and double-click on the zip file for v1.26. Click on "Yes" to install it.
3. If you see the "INVALID PLUGIN" message, go to the newly-created ShellDetails plugin folder.
4. Rename the extension of the file ShellDetails.wdx as ShellDetails.uwdx
5. Go back to the zip file for v1.26. Again, double-click to open it and click on "Yes" to install it. This time you will not see the error message.

[Dalai]

2nn1k3
Yes, that works. For step 5 one could also install the ShellDetails.uwdx via the TC Configuration dialog, in the Plugins section.

Regards
Dalai

[nn1k3]

Dalai wrote: one could also install the ShellDetails.uwdx via the TC Configuration dialog

But I found that the TC configuration plugin dialog will not install a uwdx file. So your step 5 will work only if, during step 4, I were to make a copy of the wdx file and rename that as uwdx. Only then I could use the TC dialog, but of course on the wdx file. I'm out of my depth, but reporting what I found in case it helps somehow.

[Dalai]

2nn1k3
You can type "*.uwdx" (or even *.*) into the File filter box of the Open dialog to make files of that type available for selection.

Regards
Dalai

[wiktoriano]

Hello.
How can I change the flag state or the flag color?

[Lefteous]

2wiktoriano
Is the 'Flag state' something you see in Explorer? If yes which operation system do you use?