As Chip says, the reclass process is nowadays reversible, without the necessity 
of editing the .we file; you just use Insert-R to reclass the element to 
something else that might work, or reclass it to "original class", which sets 
things back to their native state.

In trying to determine what information was available from a modern program 
using UIA, I found the GW Micro Tree View app to gbe useful.  You find a ton of 
redundant information, and I don't get much insight on how one would script the 
program, but you at least see what has been provided, its roles, states, 
parents, siblings and children.  The results can be saved to an XML file for 
further analysis.

Lloyd Rasmussen, Senior Staff Engineer
National Library Service for the Blind and Physically Handicapped
Library of Congress   202-707-0535
http://www.loc.gov/nls
The preceding opinions are my own, and do not necessarily reflect those of the 
Library of Congress, NLS.

-----Original Message-----
From: Rick Thomas [mailto:ofbgm...@mi.rr.com] 
Sent: Saturday, June 21, 2014 8:41 AM
To: gw-scripting@gwmicro.com
Subject: ReClass Question More Details

Hi:
OK, some details:
It appears WindowEyes is not focusing on the correct object likely due to 
either not using uia correctly or relying on msa which does not support modern 
UI.
It is focusing on a Wrapper object which may, from below, be a part of the 
Microsoft Framework which WindowEyes does not recognize, or has not recognized 
in the past.
Here is the information and I could use some suggestions about ReClassing this 
object but I dont think it possible since it is not a UI element but a support 
wrapper element that creates windows dynamically.

original class:
HwndWrapper[DefaultDomain;;2c922a9a-6ecb-4910-8630-004662f3
WindowStyle:
46000000
Definition of the Class:
HwndWrapper Class
  Visual Studio 2013
Represents a disposable wrapper around an HWND that can construct the WNDCLASS 
and HWND, run the WndProc
  and dispose of the
WNDCLASS and HWND.
Namespace:
Microsoft.VisualStudio.PlatformUI
Assembly: Microsoft.VisualStudio.Shell.12.0 (in
Microsoft.VisualStudio.Shell.12.0.dll)
OK, given the above I dont think this class can be reclassed since it is not 
the correct object windoweyes should be focused on.
Using the mouse windoweyes apparently can not read the Objects managed in this 
class either.
I doubt WindowEyes scripting will help without having access to the native UIA 
tree and elements since WE doesnt recognize the objects being created in the 
first place and likely cant due to the fact it is a MS Framework Object.
Any suggestions short of spending half my life trying to analyze this dom using 
some external scripting?
Rick USA

Reply via email to