Thanks Steve:
There is the Windows API, VBScript and the Windows DLLs and Framework. I use to
use the Windows DLLs to access some information about windows controls and
modify them with the DLLs.
So I sort of get making calls to Windows DLLs from a script to access system
properties or events. Now, Windoweyes says they have an API that provides
direct access to the controls of a running application like Visual Studio.
Is the definitions of the Objects in their reference document the documentation
for their API? Do you know the commands you would put into a script to find a
button with some name or handle inside a given window or dialog. Then, once
found set focus to it and pressit or fire it's activation event somehow?
The sum total I found in the GW documentation was how to display a couple of
message boxes. Nothing on interacting with controls in a running program let
alone using MSAA nor the new UIA or whatever it's called.
What is their SDK all about? I haven't seen anything on using that either.
Thanks Rick USA
----- Original Message -----
From: Stephen Clower
To: [email protected]
Sent: Sunday, February 22, 2009 1:22 PM
Subject: Re: General Concept Question
Rick,
This might work if the VWD software supports Com automation and if the
gridview control can be manipulated as an object. I honestly don't know if it
does, but the idea is sound.
You can also pull up the WeEvent script and monitor the MSAA information that
the gridview sends out and write a script to intercept and speak the data.
Best regards,
Steve
On 2/22/2009 6:45 AM, Ricks Place wrote:
Hi:
I have a GridView I want to make work better. Would I instantiate a
instance of it using the get object command?
Can I assume it's properties and methods would then be available in my
script?
Would I use a Windows Control to display a more Windoweyes Friendly version
of the Data and allow for adding new rows and cells?
Rick USA