I think you're right about the UI.
My idea will be best handled by MCs own tools, so I will need to study the MC.<command> features more closely. That could give me some great automation.
e.g. I like the ability to load the explorer panel filter via a button - "MC.Explorer.SetViewFilter" - is very useful.
So I need to play with the other commands.
I think that the ideas I had clash between using MC script & taking over parts of the MC UI environment.
I am not 100% sure of boundaries yet.
Using the "CustomCommands" you can set some part of the UI. Even if you used them in MultiScript.
But if you go crazy I think you can break things..
hehe If you learn C++ program you can create plugins instead. From there you have a lot more control
I can see DOS .bat type script is cumbersome/weak compared to the MC script, & that the script is out classed by C++ MFC.
I was more thinking that you can write stuff in .bat script but you do not change the UI of Window Explorer or other programs from .bat script
They work against the same filesystem but there are separate layers of viewing it.
I noticed on the 1481 update today that array processing by functions has changed. If I understand this correctly it looks like scripting will be quicker & easier.
That was only a bug fix when inilizing array using single quote characters instead of double.
instead of
@var $arr[] = { "string1" , "string2" }
one can write
@var $arr[] = { 'string1' , 'string2' } <<= did not work before, works is 1481+
Why single quote? if you need to have " inside the string.
Instead of writing
@var $text = "\"1\" is good" you can write
@var $text = 'string "1" is good'