WAD TCToolBar troubles

[djspits]

Writing the current toolbar defs does not produce the expected file.

Regards, DJ

 

[Charles Dye]

Does it work as expected if you give it a fully qualified pathname?

 

[vefatica]

It works here with a full path or with .\filename. But if I give only a filename (no path at all) TCMD (which writes the file) tries, and fails, to put it in c:\windows. That's peculiar since c:\windows is not TCMD's current working directory. From ProcessMonitor:

 

[vefatica]

It works here with a full path or with .\filename. But if I give only a filename (no path at all) TCMD (which writes the file) tries, and fails, to put it in c:\windows. That's peculiar since c:\windows is not TCMD's current working directory. From ProcessMonitor:

View attachment 3486

It might have worked for me with ".\" because v:\ was both TCC's and TCMD's current working directory. Perhaps, in djspits's case TCMD's CWD was somewhere in the "Program Files" tree ... and TCMD tried to put it there ... and failed.

 

[Joe Caverly]

The Toolbar problem was seen earlier this year;

Testing for presence of Toolbar

Joe

 

[rconn]

The toolbar is a Take Command component, not TCC. So it is executed inside Take Command, and (if you do not specify an explicit path) it will use the current default directory for Take Command.

So, unless you know Take Command's default directory, use an explicit pathname, not a relative one, for TCTOOLBAR /W.

 

[Charles Dye]

Suggestion: TCTOOLBAR /W should canonicalize the filename before passing it to Take Command. (Doing so would also provide support for directory aliases.)

 

[rconn]

TCC doesn't (ever) do anything with any of the TCTOOLBAR arguments; it just passes everything to TCMD. Trying to preprocess them would require a whole lot of back & forth with TCMD, and would be of minimal benefit.