There are two completely separate issues being discussed here.
One issue is about alleged limitations when the powerpro.exe
command line parameter is a built in command.
Alex wrote:
AP> the only way to call a script with arguments
AP> from the command line is like this:
AP> .\PowerPro.exe *Script Quit (.MyScript("Arguments"))
Ted wrote:
T> IMHO, the best way now is using ppbang.exe. For example,
T> I only know of this way to do the following:
T> ppBang.exe [EMAIL PROTECTED]("Arguments")
Actually, the following works:
powerpro.exe [EMAIL PROTECTED]("Arguments")
It's just that the command line prefers the complete form
of a command instead of the abbreviated shorthand forms.
Thus it requires *Script before script commands.
use: Script assign this that
instead of: this = that
______________________________________________
Discussing a switch (to indicate whether a powerpro.exe
command line parameter is a .pcf file or a command)
is a different issue, which is currently irrelevant.
That is decided by whether PowerPro is already running.
A switch would only be required if PowerPro.exe accepted
"either or both" kinds of parameter, whether it is currently
running or not.
Taking Sean's proposal for example (-i switch required before
a .pcf filespec; no switch required before a command);
it could work like this:
-- When PowerPro is not running --
powerpro command.action(args) ;; starts PP and runs the command
(presumably after completing any scheduled Startup items).
powerpro -iC:\path\...pcf ;; starts PP using the specified pcf.
powerpro -i"C:\path\...pcf" command.action(args) ;; does both.
-- When PowerPro is running --
powerpro command.action(args) ;; runs the command.
powerpro -iC:\path\...pcf ;; switches to using a different pcf.
Maybe that would need a confirmation dialog:
"PowerPro is already running with name.pcf.
Switch to using othername.pcf?" Yes/Cancel
powerpro -iC:\path\...pcf command.action(args) ;; does both
i.e. switches pcf (with confirmation?) then executes the command.
____________________________________________
As Alex noted in his original post, this is not urgent.
It's just a future possibility for an enhanced command line.
After a marathon of new features, Bruce is currently focussed
on consolidating the features already in 4.1 RC.
Anyway, no changes are actually *needed*.
For example you can change the pcf in a running powerpro with:
powerpro.exe *Exec ChangeConfiguration filespec.
And you can run a script with an @label entry point and args
as demonstrated above.
The current command line is fine, provided you are aware of
whether PowerPro is already running; and ppbang and ppbangonce
are quite good as workarounds if you are not.
Admittedly, ppbang offers less than the possible enhancements to
powerpro's command line described above, and seems less available
and friendly to new or intermediate users.
------------------------ 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/
