L.D wrote:
>MIME.CFG tells Arachne what to do when certain things happen, including
>functions which can be called with a hotkey, yes? Yes ...
It can specify a pressed hotkeys? Here I thought I knew how mime.cfg
worked... How do you specify a pressed key then?
>A line in MIME.CFG can contain more than one command, many times
>using CR "/n" to separate them, yes? Yes ...
Nope, it's "\n" to seperate them.
>So why not modify clear_cache line by appending [after the three $
>variables] /n for 'Enter' and the command in the toolbar for load
>images, Ins?
Because the "command" is the key "insert" on the keyboard. Exactly what did
you write in mime.cfg? mime.cfg can AFAIK NOT ever pass this to the BIOS
keyboard buffer. Trying to implement that would, this is my guess of
course, take much more time than anyone could possible gain on it.
>Why NOT?? Cuz you end up with all the files in main directory erased.
Please... give me the line that you wrote. Since I (still) find this
completly impossible to do. My guess at this moment is that you put "ins"
at the end of the mime.cfg statment and somehow you had a command (BATch
file perhaps?) that's called "ins" that removed all the files.
I may be wrong (but I'm 99.99% sure I'm not)...
Your line looked something like this:
file/clearcache.dgi |call $esystem\\dgi\\clr.bat $c $a $t/n ins
Which is:
1. Wrong
2. Unsafe (who knows what the for loop in clr.bat will do when it gets
"c:\temp/n" as arg3 ?
My conclusion is that you have missunderstood this and screwed it all up.
This is not Arachne's fault, there's nothing in the documentation that
indicates how you choose a key to be pressed during a mime.cfg call. The
warning should, if even it should be considered one, be to NOT assume that
a program can do something that nothing backs up and that users try things
at there own risk if they are jumping to conclussions. Perhaps the
documentation is bad - what do I know, but I can not see any way in how you
can mix up the docs for mime.cfg and toolbar.tb
