Code: Select all
Command: V:\bin\PowerPro\pp0.exe
Parameters: .tc@bar2menu(?'%%COMMANDER_PATH%%\cmd\CMD.BAR',?'-P %P -N %N -L %L -T %T')
Moderators: Hacker, petermad, Stefan2, white
Code: Select all
Command: V:\bin\PowerPro\pp0.exe
Parameters: .tc@bar2menu(?'%%COMMANDER_PATH%%\cmd\CMD.BAR',?'-P %P -N %N -L %L -T %T')
Whatever Christian does his programme will not be able to launch a commandline if its length exceeds the limit defined by Windows (version dependant).sgp wrote:I think it depends on the maximum length of the Parameters after %P %N etc are expanded. Can this limit be increased in the next build?
Thank you for finding the exact limit. Your program starts but I think it's just unpredictable, here the same program and same command line some times starts and some times doesn't - checked with process explorer.m^2 wrote:Tested.
My program starts, but it's command line is cut to c.a. 259 characters. (ADDED: Exactly 259 characters.) Maybe PowerPro refuses to start with incorrect command line?
I really think that there's a bug somewhere in this interface. It behaves inconsistently. For instance, if I start tc7pb4 and immediately run my command, previously defined as:ghisler(Author) wrote:Please retry now, beta 4 supports a longer command line internally.
Code: Select all
Command: V:\bin\PowerPro\pp0.exe
Parameters: .tc@bar2menu(?"%COMMANDER_PATH%\cmd\CMD.BAR",?"-P %P -N %N -L %L -T %T")
Code: Select all
Command: cmd.exe /k echo .tc@bar2menu(?"%COMMANDER_PATH%\cmd\CMD.BAR",?"-P %P -N %N -L %L -T %T")
Parameters: -P %P -N %N -L %L -T %T
Code: Select all
Command: V:\bin\PowerPro\pp0.exe .tc@bar2menu(?"%COMMANDER_PATH%\cmd\CMD.BAR"
Parameters: ,?"-P %P -N %N -L %L -T %T")
I can confirm that. But the outstanding problem isghisler(Author) wrote:environment variables only get expanded in the "command" part, while parameters like %P are only expanded in the "parameters" part. Can't you confirm that?
In fact I just did it, and this time I got an application error from pp0.exe saying that the command line is incomplete, that is the parameters line either didn't get passed to the API that started pp0.exe, or it got mongled by the API that started pp0.exe.sgp wrote:and this time everything gets correctly expanded... but then I close TC, restart it press the command button again and the parameters part isn't passed on to the command-line anymore !!Code: Select all
Command: V:\bin\PowerPro\pp0.exe .tc@bar2menu(?"%COMMANDER_PATH%\cmd\CMD.BAR" Parameters: ,?"-P %P -N %N -L %L -T %T")
Code: Select all
"D:\PP Sym\pp0.cmd" .tc@bar2menu(?"F:\totalcmd\cmd\CMD.BAR" ?"-P F:\ -N "long file name . ext" -L C:\DOCUME~1\ND\LOCALS~1\Temp\CMD9E.tmp -T F:\long dir name\")
Code: Select all
"D:\PP Sym\pp0.cmd" .tc@bar2menu(?"F:\totalcmd\cmd\CMD.BAR"
That's it! Thank you ND, you figured out the remaining cause of my problem. When the cursor is on the [..] marker TC doesn't pass the "parameters" part of the button. I think this is a design limitation that should be removed. I don't see why TC should pass "parameters" when a file is selected and not pass "parameters" when [..] is selected. Look at my case, "parameters" includes syntax characters that are always needed regardless of which target file/[..] is selected.ND wrote:When pressing the button while the cursor is on the "parent dir" [..] marker...
... the %parameters are not passed to the command line anymore.