Hi guys,
I fully understand how bad this must sound so close to a release, but
I'm not suggesting that it's anywhere near urgent!
--- Sean wrote:
> Indeed * for built-in commands is not needed anymore if used inside
> PP. However, it's still needed if used as a commandline parameter:
> ...\powerpro.exe *Script RunFile ...
> ...\powerpro.exe Script RunFile ...
Given the recent advance from the old *Asterisk NextWord Etc. syntax
to the new Plugin.Call(Oriented) approach, is it likely that we will
see this approach more easily adoptable on the command line in the
future?
At the moment, the only way to call a script with arguments from the
command line is like this:
.\PowerPro.exe *Script Quit (.MyScript("Arguments"))
I understand that the command line is also used to select a PowerPro
configuration for loading, so perhaps it would be easier if some sort
of switch were required?
.\PowerPro.exe /Cmd Plugin.Call
--
Alex Peters / Melbourne, Australia
PowerPro v4.1.00 / Windows XP
------------------------ Yahoo! Groups Sponsor --------------------~-->
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/JV_rlB/TM
--------------------------------------------------------------------~->
Attention: PowerPro's Web site has moved: http://www.ppro.org
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/power-pro/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
