Thanks Bruce: I think it may have been something else but then again, I dont
know and that's why I'm asking:
1) The state of Native UIA handling and Operations within WE and within the
Scripting Environment;
2) The state of any production External Scripts accessing what would have
been MSAA objects and properties and methods within the .net Framework;
And 3) how far along they are with handling WPF in WE.
If I remember Doug had mentioned that WPF was a high priority item on the
list of things to be done along with UIA support and the new Internet standards.
But, I dont remember him addressing conflicts in message processing as
related to external scripts but I may have just forgotten it if he did and
still would like to know if anyone has an external .net script working handling
MSAA or UIA operations in place these several months later.
Thanks for the heads up though Bruce.
Rick uSA
----- Original Message -----
From: BT
To: [email protected]
Sent: Tuesday, April 10, 2012 10:41 AM
Subject: Re: WE And Microsoft Development Environments
Hi Rick,
I think Doug himself had set during Chip's scripting class that the UI
messaging had been changed by Microsoft and was not working as expected.
I do know that changes were going to happen, but when is anyone's guess.
This could be your problem with the messaging...
Bruce
Sent: Tuesday, April 10, 2012 7:03 AM
Subject: WE And Microsoft Development Environments
Hi: It has been some time now since I mucked about with scripting.
A discussion about VS 2010 has come up on the Blind Programming list and
gave me reason to check in on this subject asking 3 questions.
First: Has WE developed full support for WPF yet, it has been a couple of
years now I have heard you have been working on it but haven't heard if you
have full support in WE and nothing about scripting;
Second: Has anyone built a fully functioning external script accessing the
.net FrameWork Objects, not just the handful available to VBS.
I tried some time ago but ran into problems with message processing and
never did get it to work properly when attempting to work with MSAA Objects,
Properties and Methods, finally having to give up due to time constraints.
Note that PowerShell and all the .net languages have full access to the
.net FrameWork objects, properties and methods if I remember correctly.
Other languages may be an option as well but I am most familiar with the
above development environment.
Finally: There is the ongoing question about Native UIA support. Aaron said
some of it is being folded into the MSAA Object; But, I would like to know when
actual support will be available if possible since everything Microsoft is
putting out is now using UIA, WPF and, of course, the .net FrameWork.
Anyway, I wanted to respond in a more accurate manner to the thread on the
Blind Programming list about using the WindowEyes Scripting Platform and
scripting of Visual Studio 2010 and all the other Microsoft DeskTop, Mobile,
Web, DataBase and Project Management Development packages that are now using
WPF, UIA and the .net FrameWork.
Thanks:
Rick USA
