Examples:
Code: Select all
Command: %comspec% /k echo
Command: pspad.exe X:\file1
Moderators: Hacker, petermad, Stefan2, white
Code: Select all
Command: %comspec% /k echo
Command: pspad.exe X:\file1
See also: http://www.ghisler.ch/board/viewtopic.php?p=99245 - es stimmt aber nichts! - at least I can't make it work for files on my local harddisk.If you don't use parameters and drag something to a button, the short name is passed to the program (%p%n).
Of course you can, just write %p%n in parameter field...I hope it stays that way, otherwise I can't drag-and-drop to buttons with some of my old 16-bit programs.
This is outdated information:If you don't use parameters and drag something to a button, the short name is passed to the program (%p%n).
IcfuHISTORY.TXT wrote:26.01.07 Added: Button bar: When dropping a file to a program on the button bar, pass the long name instead of the short DOS name 8...]
You are right! - SorryThis is outdated information:
So it seems that TC detects if the program in the Command field is 16-bit, which explains why d&d to my 16-bit programs still works without a %p%n parameter.26.01.07 Added: Button bar: When dropping a file to a program on the button bar, pass the long name instead of the short DOS name to the program (in double quotes "" if needed) if the program isn't an old 16-bit program. If this causes problems, put %p%n in the parameters field of the button
Code: Select all
Command: %comspec% /k echo
Parameters: %P%S
No idea what happened to my quote, something went wrong when copying & pasting, very strange.But the whole quote is:
Nope, the problem with 8.3 filename is ONLY when in the COMMAND field there is a parameter behind program.exe!It must also mean that TC considers cmd.exe to be a 16-bit program !? Is your pspad.exe 16-bit?
Code: Select all
Command: pspad.exe
Right - I can confirm that with PlainEdit.exethe problem with 8.3 filename is ONLY when in the COMMAND field there is a parameter behind program.exe!