[WCX] API How to get options setting by user in pack dialog

[vserd]

Howto in wcx plugin I can get info for set of user choice archive settings?
as Also pack path name (only recursed), Recursively pack subfirecroties, Multiple disk archvie, Create SFX and all others?

In WCX Writer's Reference.hlp I not found this info.

[Lefteous]

2vserd
Hi,

Howto in wcx plugin I can get info for set of user choice archive settings?

There is function ConfigurePacker which can be used to display your own packer options dialog.

pack path name

Check the parameter Flags in PackFiles if it contains PK_PACK_SAVE_PATHS.

Recursively pack subfirecroties

Total Commander will give you the proper target filenames in ProcessFile.

Multiple disk archvie

An easy way is to check if the user has entered exe as file extension. This is what happens when this option is checked.

[vserd]

2 Lefteous

There is function ConfigurePacker which can be used to display your own packer options dialog.

If options in Pack Dialog avaible, why I must duble in own interface? Its bad design.

An easy way is to check if the user has entered exe as file extension. This what happens when this option is checked.

h.m. I think of this.


Found BUG in Inteface.
If I try set packer to plugin or non zip packer and them set chekbox "create sfx", packer changed to zip.
Sample
after show dialog
zip:"D:\WCX Writer's Reference.zip"
chek tar:
tar:"D:\WCX Writer's Reference.tar"
chek "Create SFX":
zip:"D:\WCX Writer's Reference.exe"
second chek tar:
tar:"D:\WCX Writer's Reference.exe"
Unchek "Create SFX":
tar:"D:\WCX Writer's Reference.tar"
chek "Create SFX":
zip:"D:\WCX Writer's Reference.exe"

[Lefteous]

2vserd

If options in Pack Dialog avaible, why I must duble in own interface? Its bad design.

I agree partially. TC should ask the plugin for supported options and build the user interface based on this information. On the other hand plugins may have options which can be quite specific or even unique. More common options are required but a packer-specific dialog as some kind of extended option dialog is definetely necessary.

Found BUG in Inteface.
If I try set packer to plugin or non zip packer and them set chekbox "create sfx", packer changed to zip.

This bug is well known I think (isn't it?) and I hope it will be be fixed in TC 7.0 (along with a new more general option caption).

[vserd]

2 Lefteous

I agree partially. TC should ask the plugin for supported options and build the user interface based on this information.

Its Ideal solution, but not achieve (ralize).

On the other hand plugins may have options which can be quite specific or even unique. More common options are required but a packer-specific dialog as some kind of extended option dialog is definetely necessary.

If TC realize base set of options, well know to users, plugin do not need double it, plugin shuld get user choice. Packer-specific options must realize in our configure dialog, and get from our mechanism.

This bug is well known

I do not know of this . Where I see list of founded bugs?