There is still an issue with the TCTOOLBAR command. I tried running
tctoolbar /w tctoolbar.cfg
There was a pause, as if something were being written, but the file did
not exist in the current directory. When I ran
tctoolbar /w c:\temp\tctoolbar.cfg
the file was found in the temp directory.
A scan of my entire hard drive turned up another one in the default home
directory of my TCC configuration. This looks like a bug to me. I would
expect the file to be written to the current directory if no target
directory is specified.
Even the command
tctoolbar /w .\tctoolbar.cfg
writes the file to the default directory rather than the current directory.
I can confirm that the format of the file has been fixed. I'm still
puzzled, however, by the flag values stored. The help file for the
TCTOOLBAR command says:
The flags parameter specifies what happens when you click
the button. If flags is 0, Take Command will use command to
start a new tab (or a new window if command is a GUI app).
If flags is 1, the command text (in KEYSTACK format) is sent
to the current tab. If flags is 2, the button will change
the default directory in the Folders view. You can
optionally add 4 to the value of flags to insert a separator
before the button.
You seem to be adding 256 to all the codes when they are written out by