Proxomitron and Network Commands

[4Access]

sidki3003 Wrote:All commands are listed in a section of the compiled source. There are two undocumented ones.
$TYPE(xml) doesn't seem to have any effect, probably an unfinished project.
$EXEC(something) is operational and controversial, as you can imagine. Use it wisely.

When I heard this I was convinced Proxomitron's potential had increased ten fold! This was by far the most valuble "undocumented" feature I'd heard of for Prox! You really made my day!!

sidki3003 Wrote:Right - the thing is that $EXEC doesn't take any parameters besides the file or URL. You'd - luckily - need a helper app to make real use of it.

Then you had to go and say that, which nearly ruined my day, since I wanted to be able to pass parameters to the program called by $EXEC. <_<

But your comment about a "helper app" got me to thinking, and a that's when I realized that a combination of $EXEC & $ADDLST could get me what I wanted.

Basically my idea now is as follows:

• Create a blocklist called something to the effect of: ProgParms.txt</li>
• Use $ADDLST to place into ProgParms.txt any parameters I'd like to pass to my program.</li>
• Have $EXEC call a batch file that parses the contents of ProgParms.txt & then launches my program, passing to it the contents of ProgParms.txt</li>
• Finally, have the batch file clear the contents of ProgParms.txt so that it is ready for the next command!!</li>

While I've yet to try it, I can't think of any reason this wouldn't work. Does anyone have any experience doing something like this? Maybe there's an easier way? I'm curious exactly what you had in mind when you mentioned that helper app sidki...

Anyway, thanks for the info!!! IMO $EXEC really has the potential to expand Proxo's power. In the end you really did make my day! [wub]