Clarence,
thank you for your latest issue of "Arachne Minimalist" at Arachne's
homepage on the mime.cfg secrets. I am tempted to say that the
second most interesting thing that from time to time happens in
computer science is a new issue of your column.
I found your article very enlightening even if this topic is not
entirely new to me. It seems to me that Arachne users interested in
these less documented features of the program have no other way than
find something out on their own by time swallowing experiments. Even
if the secrets of mime and dgi are not always the product of a
logical thinking mind, I wonder whether we could share some of these
problems on the list.
So, list, here is my still undiscovered secret:
I have noticed a strange behaviour of Arachne when calling
dgi-procedures.
On one page for offline use I have linked an input form to a dgi
program that expects three command line parameters. The parameters
are sent to a batch file that according to the input selects the
correct page to display.
Everything works smoothly unless I happen to touch the 'R' key.
The attempt to reload the dgi page fails, because in this case the
input from the form is missing. So far it seems quite logical. But
when I tried to fix my batch file for the case of missing input I
noticed that Arachne does send parameters. Instead of three
parameters when calling the dgi from the form, in case of reload
it gets only one, and it is exactly the first character of the
last input.
My questions:
- when and from what is the $s parameter created?
- is there an elegant way to prevent Arachne from reloading a
dgi file?
- is this this strange behaviour a bug? (pardon, Clarence, I am still
addicted to the CSS-toy version 170rev3)
Regards
Christof Lange
________________________________________________________________
Ceskobratrska cirkev evangelicka - Betlemska kaple na Zizkove
Prokopova 4/216, 130 00 Praha 3, Czech Republic
Tel. (00420-2) 22 78 06 73 / 22 78 20 02
http://www.volny.cz/cce.zizkov
