Pack files in place and custom packer extensions

[milo1012]

There is some ugly glitch with the "Pack files in place" function and custom packer extensions.

Pack in place means "create the archive in the source directory instead of in the target directory".
This means either when pressing Ctrl and using the "Pack files" button
or when manually removing the path to a file, i.e. when changing:

Code: Select all

bzip2:"c:\dir1\file1.txt.bzip2"

into

Code: Select all

bzip2:"file1.txt.bzip2"

Now, select Create separate archives, one per selected file/dir
and

Code: Select all

bzip2:"file1.txt.bzip2"

is changed to

Code: Select all

*.*.bzip2"

(missing starting quotation mark)

This would result in file1 being merely copied to file1.txt.bzip2,
so if you're not watching what is entered in the path box, files with wrong extensions can be created.


Things can get even weirder when you now select another extension, e.g. .cab:

Code: Select all

cab:*.*.CAB"

Now deselect Create separate archives, one per selected file/dir
and we get:

Code: Select all

cab:bzip2:"file1.txt.CAB"

This only seems to happen with custom packer plugins and extensions, internal formats (zip, tar,...) don't seem to be affected.

Tested with TC 8.51a 32bit.

[ghisler(Author)]

I will check it, thanks.

[milo1012]

21.11.14 Fixed: Pack dialog (Alt+F5): Packer prefix lost when packing to same dir and clicking on "Create separate archives" for packer with 5 or more characters (e.g. bzip2) (32/64)

Fix confirmed (both 32/64).

[ghisler(Author)]

Thanks!