Plugin path

[Giovanni]

Specifying plugin path names differs between versions.
Example, plugins are stored at: %COMMANDER_PATH%\Plugins\

[ListerPlugins]
0=%COMMANDER_PATH%\Plugins\wlx\myplugin.wlx64
1=Plugins\wlx\myplugin.wlx

With 32bit, you can specify relative folder (just like TC7.5x)
With 64bit, you have to specify %COMMANDER_PATH%\

[Giovanni]

I found this in history.txt:

Code: Select all

14.08.11 Added: When browsing for plugins, also look for extension with '64' at the end. Cut off the '64' if there is a 32-bit plugin with the same name in the same directory (64)

So I changed the .ini file to this:

Code: Select all

[ListerPlugins]
0=Plugins\wlx\myplugin.wlx 

Works with 32bit only.

Changing to this

Code: Select all

[ListerPlugins]
0=%COMMANDER_PATH%\Plugins\wlx\myplugin.wlx

Works with 32bit and 64bit.


IMHO I think that the 64bit version should be adapted to work just like old versions without the need for %COMMANDER_PATH%\

[petermad]

This was a known bug for TC 8.0 beta 1 - have you tried beta 2 ??

[Giovanni]

Yes - this is using beta 2.

[petermad]

2Giovanni

Sorry, after reading your report again, I can see that it is not the same bug - the other bug was about TC 8.0b1 x64 not being able to use %%COMMANDER_PATH% for content plugins.

I can confirm that relative path doesn't work any more in TC 8.0b2 x64.

[ghisler(Author)]

Hmm, it's probably just a coincidence that relative paths work in 32-bit. I will check whether I can support them also in 64-bit.

[ghisler(Author)]

I have decided NOT to support this, sorry. Please use the %commander_path% variable. It seems that the 64-bit dll functions are more cautions with the locations from which they load dlls.