PowerPro & AutoIt (was AutoIt)
- Sheri, Mike
Here's the URL to PowerPro's yahoo-list
One of its users (and a couple of others - with me cheering from the
sidelines and waiting till its complete is putting together a tutorial
on PowerPro scripting
here: http://groups.yahoo.com/group/power-pro/ - Have a look in its
Files section. Its still a work in process but Alexandros is trying to
make the scripting capabilities more accessible.
The author just converted from HLP help to CHM help. From the CHM help:
>>Running Built-In Commands from the Command LineYou can run built-in (*) commands from a command line. This could be
used to execute PowerPro commands from shortcuts or batch command files.
PowerPro must already be running. Type the built-in command, action, and
parameters on the command line. For example
C:\program files\PowerPro\PowerPro.exe *Menu Show MyMenu
shows menu MyMenu from the running PowerPro program
>>Sending Keys to Other WindowsSamples
Use the *Keys command to send keystrokes to other windows. Sending keys
can be used to send text to the receiving window or to automate
functions of the receiving window. For example, functions on menus can
often be accessed by Alt-ab where a is the first character of the menu
name and b selects an item on that menu.
The problem is I don't really know enough about either to be sure what
can be done in one and what can be done in the other, let alone which
My understanding of what you were doing:
A clip initiates an autoit script which raises a dialog which you can
interact with to tell the clip to continue, abort (or possibly (?) send
it some additional info) replacing the native mechanisms that clips have
to communicate with the user. Approximately correct?
again from PPro help:
>>Prompting for Yes/NoUse *Exec Prompt to prompt for a Yes/No answer an set a flag with the
result. For example:
Parameter14 Any text
displays a message box with "Any Text" and sets flag 14 according to
whether the result is yes or no.
You can also prompt for a yes/no/cancel result by using a variable
instead of a number:
Parameterc Any text
Displays a yes/no/cancel dialog and sets c to 0 for no, 1 for yes, 2 for
I'm not too sure about modal vs non-modal (ie (?) whether the other app
is waiting on the AutoIt or can proceed while the AutoIt message-box is
sitting there waiting to pass a message (?))
>>modalMode oriented. A modal operation switches from one mode to another.
Contrast with non-modal.
>>non-modalNot mode oriented. A non-modal operation moves from one situation to
another without apparent mode switching.
I always get these confused. In Notetab, the Find is non-modal and the
Options is modal. Have I finally got that straight or is it the other
Regards ... Alec
---- Original Message ----
From: "Sheri" <silvermoonwoman@...>
Sent: 25 September, 2002 10:11
Subject: Re: [NTS] AutoIt
> --- In ntb-scripts@y..., "Alec Burgess" <burale@a...> wrote:->
>> Have you used / compared PowerPro to AutoIt!? I've been
>> lurking on both lists without actually using either for
>> writing/running scipts. I'd got the impression that PowerPro
>> was more "powerful" and "flexible" though maybe its just the
>> impression I get from the tone of the user groups.
> Hi Alec,
> This is the first I've heard of PowerPro. I loaded it last
> night. If it has similarities to AutoIt, I couldn't find them;
> what in particular are you thinking of? Obviously its primary
> focus is its menu'ing shell interface, but I do see that it
> has scripting as well.
> My AutoIt example showed using an AutoIt message box in a
> Notetab clip; I can't even find message box capability in
> PowerPro. The Message Box I used was only one of many
> variations offered in AutoIt. Mine had "OK", and it stayed
> topmost but didn't demand the focus. Among the many available
> options were:
> OK, OK-Cancel, Abort-Retry-Ignore, Yes-No-Cancel, Yes-No,
> Retry-Cancel Icon:
> None, Iconhand, Iconquestion, Iconexclamation, or Iconasterisk
> Applmodal, Systemmodal, Taskmodal
> That's a lot of flexibility <g>
>> I wasn't positive that PowerPro even had a command line
>> interface but it looks like (from a search of the Help) that
>> it is there.
> Again, please give an example. I'm not disputing you, but I
> can't find that either <g>. Does the menu/shell have to be
> resident to use command lines?
> ------------------------ Yahoo! Groups Sponsor
> ---------------------~--> Sell a Home with Ease!
> Your use of Yahoo! Groups is subject to
- --- In ntb-scripts@y..., "Alec Burgess" <burale@a...> wrote:
> My understanding of what you were doing:Well, not really...
> A clip initiates an autoit script which raises a dialog which you
> can interact with to tell the clip to continue, abort (or possibly
> (?) send it some additional info) replacing the native mechanisms
> that clips have to communicate with the user. Approximately correct?
If that were it, I would have used a Notetab wizard or prompt or info
The modality issue was central to solving my problem. All that
AutoIt did was provide a window that stays on top of Notetab, but
still allows Notetab to be used for editing and other purposes. The
Autoit command is over as soon as the message box is drawn. Then the
Notetab clip is checking to see if the named window is active. As
soon as its gone, it resumes processing. If there were multiple
possible responses (e.g., OK or Cancel) I'm not sure if I could read
them with Notetab or not. I think AutoIt is using DOS variables and
error levels, so it might be possible to read them with Notetab
commands (but probably not, because it would be in a different shell
space). I could always put the response on the clipboard for Notetab
> I'm not too sure about modal vs non-modal (ie (?) whether the otherI don't really understand the term either. I just know that with the
> app is waiting on the AutoIt or can proceed while the AutoIt
> message-box is sitting there waiting to pass a message (?))
4096 value (which AutoIt calls "system modal") it stays on top
without hogging the focus. When its "application modal" (value 0)
nothing else can be done until "OK" is pressed. Because I was
using Notetab's ^!Shellwait command I was able to see that the
AutoIt "script" was over even though the message box was still up.
Its not waiting for the response, my guess is: because I'm not
testing for one. I see it as a plus that AutoIt is small and doesn't
require anything be kept memory resident to use it.