Removed

Discuss and announce Total Commander plugins, addons and other useful tools here, both their usage and their development.

Moderators: white, Hacker, petermad, Stefan2

Post Reply
User avatar
norfie
Power Member
Power Member
Posts: 1194
Joined: 2003-02-18, 14:18 UTC

Removed

Post by *norfie »

Last edited by norfie on 2004-09-10, 19:30 UTC, edited 1 time in total.
User avatar
André Martin
Senior Member
Senior Member
Posts: 245
Joined: 2003-02-05, 15:46 UTC
Location: Dresden, Germany

Post by *André Martin »

You can change the IniFile path of a plugin only if this plugin follows the new plugin IniFile path standard which was introduced in TC 5.51. The new standard says that plugins can use a shared ini file (fsplugins.ini for wfx plugin and pkplugins.in for wcx plugins) which is located in the same directory as your TC/WC IniFile. The plugin retrieves the path information directly from TC. If you change the path of your TC/WC IniFile then you change automatically the path of the shared IniFiles. Unfortunatily only a few plugins follow this new standard e.g. HTTP SmartBrowser or the POP3/SMTP EmailPlugin...
Browse the web with the HTTP SmartBrowserPlugin
Check your mails with the POP3/SMTP EmailPlugin!
User avatar
Valentino
Power Member
Power Member
Posts: 706
Joined: 2003-02-07, 00:21 UTC
Location: Ukraine

Post by *Valentino »

André Martin wrote:The new standard says that plugins can use a shared ini file (fsplugins.ini for wfx plugin and pkplugins.in for wcx plugins)
Just want to add (for developers who haven't read interface reference yet) that you can change suggested ini file name (fsplugins.ini, pkplugins.ini) but recommended to keep the path. I also would like to see this behaviour in all plugins.
User avatar
norfie
Power Member
Power Member
Posts: 1194
Joined: 2003-02-18, 14:18 UTC

Post by *norfie »

Last edited by norfie on 2004-09-10, 19:31 UTC, edited 1 time in total.
User avatar
André Martin
Senior Member
Senior Member
Posts: 245
Joined: 2003-02-05, 15:46 UTC
Location: Dresden, Germany

Post by *André Martin »

1.) I have no clue :-( The docs do not mention anything about the name of the shared wlx IniFile)
2.) You cannot tell plugins to use a certain IniFile. Only the programmer can define which IniFile will be used (either the TC suggested shared one or an own).
User avatar
fabiochelly
Power Member
Power Member
Posts: 603
Joined: 2003-02-05, 12:03 UTC
Location: Rambouillet, France

Post by *fabiochelly »

I think it's better to have the ini file in plugin's dir: like this, you can move the plugin folder from a system to another easilly.
Fabio Chelly.
#60241
Lorsqu'on s'occupe d'informatique il faut faire comme les canards...
Paraître calme en surface et pédaler comme un forcené par en dessous
User avatar
norfie
Power Member
Power Member
Posts: 1194
Joined: 2003-02-18, 14:18 UTC

Post by *norfie »

Last edited by norfie on 2004-09-10, 19:36 UTC, edited 1 time in total.
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48021
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

I recommend that you react to FsSetDefaultParams and use the path given in DefaultIniName. Just change the ini file name in that variable to the name you currently use! This way the ini file will be created in the same directory where wincmd.ini is located.

Reason: Users who use Win2k/WinXP as a normal user (not admin) don't have write rights to any dirs under c:\Program files.
Author of Total Commander
https://www.ghisler.com
Post Reply