Thanks Aaron:
I have the Automation Properties for Designer frame and the designer
window/Pane from UISpy.
So far I can hit a hot key I registered with WindowEyes and have any Control in
the Designer Read Out properly using it's UIA Automation Properties.
Baby steps but so far so good.
Thanks again Aaron and I'll try killing the process and post up the results -
likely tomorrow.
Rick USA
----- Original Message -----
From: Aaron Smith
To: [email protected]
Sent: Friday, May 04, 2012 10:41 AM
Subject: Re: Stopping An External Script
As long as you kill your process, you've done what you need to do. Once you
do that, if you're still listed in the app manager, try pressing F5 a few times
to refresh the list. If you never go away, then it's probably a Window-Eyes bug.
Aaron
On 5/4/2012 10:23 AM, RicksPlace wrote:
Thanks Guys:
I dont think an external script can access the WE Script object.
Bruce, I am able to pull that information but my question is
How to stop The Script's executable and have it stopped in the WE Script
Manager.
I can stop it manually (actually I think I disable it) in WindowEyes Script
Manager but this is a pain to do over and over and bad practice.
The other thought that comes to mind is to try and Kill the VBNet2010Script
process.
But, WindowEyes might not be aware the process has stopped and leave WE
ScriptManager UI elements and, or, other variables set incorrectly.
There has to be some WE Designed way to break the connection between an
external script and WindowEyes to manage WE data integrity in case of an
external script crash.
Rick USA
----- Original Message -----
From: BT
To: [email protected]
Sent: Friday, May 04, 2012 8:16 AM
Subject: Re: Stopping An External Script
Hi Rick,
How about product ID, or Process ID, each should have a unique number
associated with it running.
Bruce
Sent: Friday, May 04, 2012 8:05 AM
Subject: Stopping An External Script
Hi:
I am creating a script in VB.net 2008 for VB.net 2010.
I check the ProductName and attempt to close the script if it is not
vb.net 2010 which opened it.
The Application.Exit() fires ok but the script is not stopped.
So:
I open vb.net 2008 to do some editing on the vbnet2010script, the
ModuleName is something like VBNetExpress which is the same as it is in vb.net
2010.
WindowEyes sees the VBNet module name and starts the vb.net 2010 script:
In the vb.net 2010 script I check for the ProductName containing 2010:
Since it contains 2008 I execute Application.Exit()
I go into WE ScriptManager and the vb.net 2010 Script is not stopped.
How do I stop the script without closing the vb.net 2008 IDE?
Is there some way of preventing WE from opening it in the first place?
What about killing the script process?
If not sure I will experiment but if there is a means of doing this
like the StopScript command in the script object that would be cleaner and more
efficient, especially if done before the script loads.
Rick USA
--
Aaron Smith
Web Development * App Development * Product Support Specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
