Windows command line
b.xavier at internet.lu
Mon Jan 17 14:40:54 CST 2005
That's a good one I didn't know!
Although I've resorted to easier to edit ini or cfg text files with the
instructions or paramenters. So when you run your stack as a service
application or W2K schedule, you dont need to rely on a command line call
and you can change it in between runs if scheduled for example.
Just a suggestion.
> -----Original Message-----
> From: use-revolution-bounces at lists.runrev.com
> [mailto:use-revolution-bounces at lists.runrev.com] On Behalf Of Ken Ray
> Sent: Monday, January 17, 2005 18:54
> To: Use Revolution List
> Subject: Re: Windows command line
> On 1/17/05 10:05 AM, "Frédéric RINALDI" <frederic at runrev.com> wrote:
> > Does anybody know how to allow a RRev application to be
> lauched (and
> > some paremeter passed) from a command line in Windows?
> >From Tip File0004 at
> When you launch an MC/Rev app, any command line information
> is sent to the application and is retrievable via
> *environment variables* numbered $0 on up. The $0 variable
> will always contain the path to the application you just
> launched, and the $1 will contain the first command-line
> parameter passed ($2 will be the second, etc.).
> So some simple code for this is:
> on openStack
> put $0 into theAppPath
> put $1 into theDocToOpen
> answer "The doc to open is: " & theDocToOpen end openStack
> Ken Ray
> Sons of Thunder Software
> Web site: http://www.sonsothunder.com/
> Email: kray at sonsothunder.com
> use-revolution mailing list
> use-revolution at lists.runrev.com
More information about the use-livecode