--- In ntb-scripts@y..., "Alec Burgess" <burale@a...> wrote:
> 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?
Well, not really...
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 other
> app is waiting on the AutoIt or can proceed while the AutoIt
> message-box is sitting there waiting to pass a message (?))
I don't really understand the term either. I just know that with the
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.