Jamal,
Sorry, wrong choice of words. I didn't mean "queuing" as in call our
Queue method. I mean call the install dialog non-synchronously and then
terminate yourself.
I want to see why we can't stop your script ourselves but in the mean
time, you can stop yourself with StopScript right after calling
WEDialogs.AddRemove with the WaitForCompletion set to FALSE.
Doug
Jamal Mazrui wrote:
Hi Doug,
I didn't know queuing the call to WEDialogs was necessary. If so,
why?
Jamal
On Mon, 7 Jul 2008, Doug Geoffray wrote:
Date: Mon, 07 Jul 2008 16:03:06 -0400
From: Doug Geoffray <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: Trying to fix Install Packages
Jamal,
There seems to be some deadlock issue that prevents us to closing down
your install packages script that calls into our install dialog. So
yes, you need to forcibly terminate your script by calling StopScript
right after queuing to bring up our install dialog. I did this in your
script and it worked perfectly.
Regards,
Doug
Jamal Mazrui wrote:
I appreciate the suggestions from Doug and Aaron.
Doug,
I previously tried a call to StopScript after asynchronous WEDialogs, but
the Install Packages script failed to update that way. If the code exits
the dialog procedure instead, it seems to work. Are you saying that
Window-Eyes does not stop the script unless there is a call to StopScript?
I thought it forceably stopped the script before loading the update to
Install Packages.
Aaron,
I tried the WEPMInfo object, but get the following error when calling
GetInfo:
gwtoolkit.vbs -
Line 1995 Column 21
The system cannot find the file specified.
< 0x80070002 >
Jamal
--
Doug Geoffray
GW Micro, Inc.
Voice 260-489-3671
Fax 260-489-2608
http://www.gwmicro.com
--
Doug Geoffray
GW Micro, Inc.
Voice 260-489-3671
Fax 260-489-2608
http://www.gwmicro.com
