[8b2 64x] Bug with adding 64bit wdx plugins

[Matthias030]

Maybe also wlx, wcx, wfx is affected and not only wdx. I tested with wdx plugin filediz:

I have plugin directory \plugins\wdx\filediz\ with files
filediz.wdx
filediz.wdx64

Now go into configuration->plugins and add filediz.wdx64. Instead of wdx64 the plugin filediz.wdx was added. Same occurs by using plugin auto-adding feature (open zip file and use auto install)

Another point:
In wincmd there are 2 fields:
[ContentPlugins]
[ContentPlugins64]

For filediz I get this in wincmd.ini

Code: Select all

[ContentPlugins]
1=C:\Program Files\totalcmd\plugins\wdx\FileDiz\Filediz.wdx64
1_detect=
1_date=1060796516
1_flags=0
[ContentPlugins64]
$checksum$=1362701401
1=1

Why using 2 fields for 1 plugin? Is this the right behaviour for 64bit plugins?

[MVV]

It is intentional behaviour. Not a bug.

TCx64 installs 32-bit plugin in ContentPlugins section (this section is for 32-bit plugins first of all) if it finds it and checks flag in ContentPlugins64 section that plugin has 64-bit 'brother'. It was made to allow using same wincmd.ini for 32-bit and 64-bit TC.

So, if you're using both TCx32 and TCx64, you need following:

Code: Select all

[ContentPlugins] 
1=C:\Program Files\totalcmd\plugins\wdx\FileDiz\Filediz.wdx
[ContentPlugins64] 
1=1

In such case both TC versions will load corresponding plugin version correctly.

[Matthias030]

Ah ok. I understand. It solves problem for using 1 wincmd.ini for both, x32 and x64 TC. On the other hand it is not easy to see which 64bit plugins are installed.