From: Fred Holmes 
@Date: Tue, 14 Jan 2003 10:35:37 -0500
@Sender: semware-owner{at}sawasdi.apana.org.au



I can't see passing a command line parameter to an autoload macro from the 
listing in the autoload list.  It would always be the same, so just write 
that parameter into the macro code itself (and rename the macro to 
distinguish it from the general one, if appropriate).   While I can't think 
of a specific example right now, one could perhaps want to pass a command 
line parameter to an autoload macro from the g32.exe command line???

Fred Holmes

At 08:41 AM 1/14/2003, Sammy Mitchell wrote:

> >Oops! Coming straight from v2.0 macro command lines are new
> >to me, so I guess I thought that the input field for
> >entering the new macros to the Autoload list was so long
> >because the extra space was for command line arguments. So
> >much for the "intuitive interface." :)
>
>Just to make sure I'm clear, you'd type your macro name as
>now, and then anything to the right would be passed as a macro
>command line?  As in:
>
>foo this is a command line
>
>Foo would be the macro, and "this ..." would be passed as
>the macro command line?
>
> >Maybe you can put
> >this on the todo list for v4.1, along with "imbedded
> >LoadMacro command lines" and "imbedded macro command lines
> >for DOS command line options /l and /e." :)
>
>Sorry, I'm not sure what you mean here.  Imbedded where?
>
>--
>Sammy Mitchell
>
>--
>TSEPro mailing list

--
TSEPro mailing list



---
[sawasdi.apana.org.au] (3:800/846.13)