Rick, One more suggestion: do you have the Vs app loaded? They say 2008, but I've heard they work fine also for 2010 and 2012. (I do see you're using 2013, so could you go down to 2012?)
Chip -----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
