ShellDetails 1.26 (Content plug-in)

[majkinetor !]

Ok. Ok ! Dont hurry....

U did a god job until now, nobody is forcing you !

[Lefteous]

ShellDetails 1.09 has been released.

ShellDetails 1.09

Here is an example of the new string --> numeric cast feature. You'll find such entries in the settings file ShellDetails.ini.

Code: Select all

;Cast fhe "Fragment" field to a numeric value to enable search for this field.
[{242ED098-D606-4FA8-9DDE-89AEDFE4EAD7}0]
Caption=Fragments
UseDefault=0
Cast=2
State=98  

In this example UseDefault is set to 0 to enable casts. Cast is set to 2 to cast to a numeric value.

[majkinetor !]

I can't manage it to work.

I created ShellDetails.ini (there wasn't any after installation) and paste the code from the example above. I then searched for Fragments > 1 but nothing.

I notice that now I have 4 Clusters in the list and not just the one. First is integer and other 3 are strings. I also have 2 streams one to be integer and second string (this is expected, right)

May I just notice this bad TC design:
Why I don't have second level properties in search with plugins dialog ? Why is this como list and not edit like in configure custom columns dialog. If that was possible the easiset way to convert to other values is to make second level menu named convert and that menu to contain values for string and integer or anything else (date?). So things like this would be possible in search field:

Code: Select all

Plugin          Propety                   OP     Value
---------------------------------------------------------
shelldetails    Fragments.convert.int     >      1

[Lefteous]

2majkinetor !

created ShellDetails.ini (there wasn't any after installation) and paste the code from the example above.

This is probably the reason why it doesn't work. ShellDetails.ini is created after you have added fields for the first time. When you have located ShellDetails.ini (see documentation for this) open the file and search for the field "Fragments" and edit its properties as described above. Now restart Totasl Commander or unload all plug-ins.
After restarting it should work.

[majkinetor !]

It works. Thank you.
This is the best way to search for alternate data streams on you hd.

I noticed this in ini file:

[{242ED098-D606-4FA8-9DDE-89AEDFE4EAD7}2]
Caption=Clusters
UseDefault=1
State=98
[{242ED098-D606-4FA8-9DDE-89AEDFE4EAD7}3]
Caption=Clusters
UseDefault=1
State=352
[{242ED098-D606-4FA8-9DDE-89AEDFE4EAD7}4]
Caption=Clusters
UseDefault=1
State=352
[{242ED098-D606-4FA8-9DDE-89AEDFE4EAD7}5]
Caption=Clusters
UseDefault=1
State=352

Why 3 same enteries ? When I remove last 2 they are crated again.

[Lefteous]

2majkinetor !

It works. Thank you.

OK

[{242ED098-D606-4FA8-9DDE-89AEDFE4EAD7}2]
Caption=Clusters
UseDefault=1
State=98
[{242ED098-D606-4FA8-9DDE-89AEDFE4EAD7}3]
Caption=Clusters
UseDefault=1
State=352
[{242ED098-D606-4FA8-9DDE-89AEDFE4EAD7}4]
Caption=Clusters
UseDefault=1
State=352
[{242ED098-D606-4FA8-9DDE-89AEDFE4EAD7}5]
Caption=Clusters
UseDefault=1
State=352

Yes it's the same for me. It seems all these fields exist.

[majkinetor !]

Well, I am not very informed how this shell things function, I just know it is COM and I used it a little.

You did excellent job. First time I saw this plugin I thought... ok... not so bad, but who needs this when I have most of the standard shell fields in tc default plug... then I was confused with damn_menu.... but I didn't ask how you achived that - I didn't know at the moment that Explorer have extensible fields. Now, knowing that, your plugin gets another dimension. Great work.

[empeg]

2empeg
Beside the workaround to deactivate the shell extension with too many fields I have found out the reason for the problem. It's a Shelldetails limitation and a bug. The problem will be solved in the next version.

Fixed in 1.09
Thanks.

[muck]

Dear all,

sorry for asking about Subversion/Tortoise againg (I've read all issues regarding tortoise and shelldetails 1.09 (with TC 6.54) but it seems that I'm way too dumb to manage it).
Here's my problem: I'm using Tortoise and I'd like to add the SVN-related columns in a TC custom view (hope it's the correct name -- I'm using the German version). That's what I've done so far:
- I added

Code: Select all

[Directories]
Dir_1="D:\Dokumente und Einstellungen\SVN"

in the ShellDetails.ini (residing in the plugins directory) -- btw: does it have to be quoted when the path contains blank?.
- I made a new custom view with a new column named "SVN Status". When I use the "+" button to select the field content ("Feldinhalt" in German, don't know the correct title in English TC) and select shelldetails there are no SVN fields.
In Explorer I have "SVN Autor", "SVN Status" and so on. My question is: which is the correct way to show these columns? If they are not displayed in the shelldetails tab, I guess there is something wrong with my configuration (regarding the directory). But if not -- which are the correct strings (refering to the "[{B725F130-47EF-101A-A5F1-02608C9EEBAC}12]" strings in the shelldetails.ini) to add these columns?

Sorry for the amount of text, I hope I made it clear.

Kind regards,

Muck

[Lefteous]

2muck
Hi,

ShellDetails.ini (residing in the plugins directory)

It's important that you check if this is really the ShellDetails.ini used. Are there any other Shelldetails.ini files for example in the directory where Wincmd.ini is located? Possible ShellDetails.ini locations are described in the documentation: http://www.lefteous.de/tc/docs/shelldetails/liesmich.htm#inilocation

does it have to be quoted when the path contains blank?

It doesn't matter. It should work with or without quotes.

Code: Select all

[Directories]
Dir_1="D:\Dokumente und Einstellungen\SVN" 

Your entry looks fine so far. Please make sure the directory is really a subversion repository not a directory containing directories which are repositories.
More information about this in the documentation:
http://www.lefteous.de/tc/docs/shelldetails/liesmich.htm#fieldsearchdir

BTW: There is also a German support thread if you prefer support in German:
http://www.ghisler.ch/board/viewtopic.php?t=9525

[muck]

Hi Lefteous,

It's important that you check if this is really the ShellDetails.ini used. Are there any other Shelldetails.ini files for example in the directory where Wincmd.ini is located? Possible ShellDetails.ini locations are described in the documentation: http://www.lefteous.de/tc/docs/shelldetails/liesmich.htm#inilocation

There was another shelldetails.ini in c:\windows. After deleting it, it was reestablished so I changed that one and deleted the one in the plugins directory.

Now it works. Thanks for the quick support.

Regards,

Muck

[Lefteous]

ShellDetails 1.11 is ready for download:

ShellDetails 1.11

Changes since 1.10:
FIXED Accidentally disabled field detection.

[zeflash]

Hi Lefteous

I'm getting an error everytime I go into a view using ShellDetails.wdx.
It says:

Note to plugin writer of plugin ShellDetails.wdx
Invalid character "." in Plugin Field "!Other P_O.box"
Please Change!

This msgbox shows once in every TotalCommander session.
I believe you are the plugin writer

Is there something I can do to prevent that? I do have a Other P_O.box field shown in shelldetails.wdx, although in the CVS view I use this field is not shown.

[Lefteous]

2zeflash
Hi,

The problem here is that certain characters are not allowed as field names. ShellDetails has not a hardcoded list of fields. Instead they are retrieved from the system. ShellDetails already contains are routine to substitute invalid characters in field names but it seems I have forget to add the "." character.
I will try to fix this as soon as possible.

[Lefteous]

2zeflash
I have a question. Did you change anything manually in your ShellDetails.ini?
Could you please provide your ShellDetails.ini. Thanks!