WdxInfoPacker.wcx kills TC without any notification

[nevidimka]

I installed the plugin WdxInfoPacker.
If I press ALT+F5 (cm_PackFiles) now: nothing visible happens, TC is busy for some seconds ("not responding") and after a short time (ca. half minute) TC is closed without any notification.
This behaviour is shown with my user account only - no such behaviour with the Admin account.

What is wrong?

(I removed this killer application and all works fine now.)

[franck8244]

2nevidimka
I think I know the reason , I'll check that.

Does your user account has writing permission to the wdxInfopacker directory ?

[nevidimka]

Does your user account has writing permission to the wdxInfopacker directory ?

No (, because it's a "Program Files" subfolder).

[franck8244]

No (, because it's a "Program Files" subfolder).

That's the problem...

I'll modify the code to use a directory where the user have write permission, Stay Tune
The plugin uses two read/write files : wdxinfopacker.ini and scheme.ini ... (at the moment located in the plugin folder)
Where should the ini file be placed ?

[nevidimka]

I'll modify the code to use a directory where the user have write permission

Thanx.

Where should the ini file be placed ?

The same behaviour like Lefteous suggested would be fit all needs.

Another problem (with Admin account) with this plugin: after "cm_UnloadPlugins" TC will be killed too.
What I did
1st start TC with runas
2nd press ALT+F5, select WdxInfo, Button "Configure", "Cancel", "Cancel"
3rd execute cm_UnloadPlugins
4th change focus to another application (TC in background)
-> TC is closed without any notification

[franck8244]

Another problem (with Admin account) with this plugin: after "cm_UnloadPlugins"

I'm aware of this problem (see the other thread about wdxinfopacker) and I'm trying to correct it right now (I have corrected it a while ago but it appears again ).
After cm_Unload has been fixed, I'll add ini file location...

Edit1 : cm_Unload has been fixed...

Edit2 : To moderators, can you "merge" the two topics about this plugin ?

[Hacker]

To moderators, can you "merge" the two topics about this plugin ?

Nope, merging is not supported in the current board config...

Hacker (Moderator)

[nevidimka]

V0.96

Edit1 : cm_Unload has been fixed...

Confirmed.

INI file: now it's chaos.

Without proper rights (in %WINDIR%) I get this error when I press "configure":
"External exception EEDFADE ... bla bla"

With proper rights in %WINDIR% the plugin take/create a new ini-files in %WINDIR% allways (regardless of another ini-files in wincmd.ini-path).

Some suggestions:
- support of %COMMANDER_PATH%
- path/name of "Scheme.ini" configurable in WdxInfoPacker.ini
- IMHO in WdxInfoPacker.ini there is no need for WdxFolder= and [PluginList] - look for this informations in the proper wincmd.ini (I don't know if it is possible.)

[franck8244]

2Nevidimka
For ini files location :
At the first launch, the plugin will look for an existing and writable file called WdxInfoPacker.ini into different location:
-Plugin dir
-TC dir
if this file does not exist or is not writable, it will create WdxInfoPacker.ini and Scheme.ini in %windir%

After the first launch the user can move those 2 files to one of the above location (where he has writing permission), this way the plugin will find existing & writable files

What location do you suggest for default creation path ?
- I'll try to "find" wincmd.ini because there you should have rights... but I'm not @ home at the moment

The exception comes because my plugin try to create file whereas the user has not the right(as you said...)

Suggestions :
-WdxFolder & PluginList in my ini : I dit it because this way, the user can use wdx plugin that he does not use within TC
(I tried to read TC ini but it's a bit complicated: read [ContentPlugin] section, then remove all "bad values" (detect string), extract plugin name and made it correspond to its path, I guess it's also why D1P uses its own plugin list in super_wdx)
-Path/Name of scheme in the ini:
Scheme.ini and wdxinfopacker used to be merged but I decided to split them for a cleaner structure.
I'll try : Scheme.ini (in the same dir as wdxinfopacker) will be the default file for scheme, if a value (don't know it's name yet) is set in wdxinfopacker then it will replace it , is that fine ?

-Support of commander path:
You mean for WdxFolder ?
As I said in totalcmd.net I'll see what I can do about that (maybe an easier workaround )

[Hacker]

What location do you suggest for default creation path ?

As nevidimka wrote, this seems to be a nice way.

HTH
Roman

[nevidimka]

- I'll try to "find" wincmd.ini because there you should have rights...

PackDefaultParamStruct ...
DefaultIniName Suggested location+name of the ini file where the plugin could store its data. This is a fully qualified path+file name, and will be in the same directory as the wincmd.ini. It's recommended to store the plugin data in this file or at least in this directory, because the plugin directory or the Windows directory may not be writable!

I'll try : Scheme.ini (in the same dir as wdxinfopacker) will be the default file for scheme, if a value (don't know it's name yet) is set in wdxinfopacker then it will replace it , is that fine ?

I think so. Background: if I have "Scheme.ini" in another folder than plugin-folder e.g. in the same folder like wincmd.ini, I will forget, that "scheme.ini" belongs to WdxInfoPacker. Therefore I want to rename it to "WdxInfoPacker_scheme.ini" or "WdxInfoPacker.sch".

[franck8244]

2nevidimka
- Is it fine if "whatever the name is" , the scheme file is always near the plugin ini file (in one of "hacker"'s location) or do you want to precise a full path ? (the 1st method would be much easier for me )

- About %COMMANDER_PATH%, is it only to use (current) TC path to search for wdx ? (eg: without fullpath, but to use "something" that will tell the plugin to look only into TC path (recursively of course))

I'll wait for your answer before I'll start to "modify" the existing code

[Wuffi]

%COMMANDER_PATH% reflects Drive and Fullpath of Totalcmd.exe
This is very helpfull if someone wants to start TC from CD or from USB-Stick!

[franck8244]

%COMMANDER_PATH% reflects Drive and Fullpath of Totalcmd.exe

I know that... instead of using %commander_path% , I can use "something else" to set wdx folder to "current" tc path...

[franck8244]

New version ( 0.9.8 ) is available

Code: Select all

Added:
- "SchemeFile=" in the main section of the ini to precise a different name than "Scheme.ini" (put only the filename not the path)
- Set "WdxFolder" to %COMMANDER_PATH% to use the current TC path to search for wdx (folder recursive)

- Selection of inifile (WdxInfoPacker & Scheme) :
Default value is located near wincmd.ini (all users should be able to write there)
otherwise it can be in (if present & writable): 
# \pluginname\*.ini from wincmd.ini
# \*.ini from TC dir
# \plugindir\*.ini
->To Know ini files, press the about button