--- In [EMAIL PROTECTED], Alex Peters <[EMAIL PROTECTED]> wrote:
> The Do() syntax can accept internal commands in any of the following
> forms:
>
> Do("*ShutDown", "Reboot NoConfirm Force")
> Do("*ShutDown Reboot", "NoConfirm Force")
> Do("*ShutDown Reboot NoConfirm", "Force")
> Do("*ShutDown Reboot NoConfirm Force", "")
You're right, those work. I thought I had tested those kind, but
it turns out not. Maybe I just (wrongly) concluded from
do("cmd","/c") and do("cmd /c","").
> It seems that for these commands, PowerPro simply combines the two
> strings anyway.
> We can already test this by executing Do("Note", ""):
> �Ԥ��Ӥ�nvalid *Note Action:�
The internal commands and plugins seem to have higher priorities
than apps in paths (:environment var.): (I have "note.exe" in win dir)
do(note.exe,"")
do("note.exe","")
> All in all, I don't think that making the second string optional will
> cause any problems for anyone.
Probably, if the 2nd parameters are of no use except the obvious role.
I'm becoming more puzzeled why Bruce didn't allowed do(cmd) then ...
------------------------ 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
--------------------------------------------------------------------~->
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/
