An internal scripting program would have direct access to internal variables like, %S.
It would be able to query the list of selected files without sending a command to TC to cause it to paste into the Clipboard -- or without parsing the ListBox which returns whole lines that aren't "tab", or "newline" delimited to split up the columns. Whereas when TC copies file details to the Clipboard, the columns of the FilePanels are hard-Tab delimited.
An internal scripting program could call cm_commands without looping through the totalcmd.inc file to match names with numbers.
An internal scripting program would be able to know what the current %COMMANDER_INI% value is, without hackish workarounds.
Now if those things were possible, the "desire" for an internal script wouldn't be so prevalent. Off the top of my head anyways.
1) And as I indicated, minimally, it would be nice for the
DetailsMode "text" that is returned when querying TC's Panel listbox be delimited by a ">" after the filename like all the other Column types are.
2) As well, a CM_Command's that would return the current %COMMANDER_INI% and COMMANDER_PATH values. They are retrievable thru hacks only - to an outside script that hasn't been launched from TC.
3) And as NSP indicated, a clean way to query the Target and Source paths.
Note: The problem with calling a script
from TC, and then passing it a list of files with %S --- if too many files are selected the whole command will fail due to a total message size limitation in how it is passed.
Whereas if the column values were ">" delimited or "TAB" delimited (like they are when the CopyFileDetailsToClip command is used. Then one could just query standard windows ListBox commands and easily be able to determine what the
file is and even what the values of the other columns are.
Also, as far as I can tell. The TABS aren't queryable for the text name. Apparently TabBoxes are protected from outside processes from even reading them.
so:
4) A way to query the current active Tab name, without resorting to parsing the wincmd.ini file and matching the TabBox number with a possible value in the wincmd.ini.
-- I am able to get the tab-index, and current Tab number. Just cannot get what the Tab has been named.
Anyways, that's my 0.04cents
