[solved} %P%N doesn't always work for some internal commands

[petermad]

Using %P%N as parameters (in button, start menu or user command) doesn't work if there are spaces in the path or file name for the commands: OPENTABS, OPENTABSL, OPENTABSR, APPENDTABS, APPENDTABSL, APPENDTABSR and OPENBAR.

Changing %P%N to %p%n or %P%n solves the problem for spaces both in path and file name, while %p%N only solves it for spaces in path name.

The disadvantage of using %p%n is that when used with OPENBAR a new .br2 file with the 8.3 filename is created.

%P%N works fine with other long filename names - it seems only to be names / paths with spaces that doesn't work.

[ghisler(Author)]

This happens because %P%N is automatically surrounded by double quotes when the name contains spaces - and most Windows functions fail when the path is surrounded by double quotes.

[MVV]

I think it is not so hard to remove quotes from all parameters accepted by internal commands:)

[ghisler(Author)]

Sure, that's why I moved it to "confirmed bugs"...

[petermad]

Fixed in TC 7.55pb3

[ghisler(Author)]

Thanks!