John (and rick), Ok; I mis-read your response, yes, you didn't say "fine", just this particular aspect was working as expected.
Do you know John, does the current VS app help things in 2013? If you disable it are things worse? It would be good to know if someone wanted to try and fix things should they start by expanding this current app, or start over from scratch? Thanks. Chip -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Saturday, June 21, 2014 3:22 PM To: [email protected] Subject: Re: ReClass Question More Details There are many things which don't work in vs, the worst of which is intellisense. Right now, you lose the cursor and have to alt-tab away and back to get it again (or at least last time I tried it). Chip Orange <[email protected]> wrote: > Hi Rick, > > Since John says this is working fine for him, is it possible you've disabled > the use of UIA in your wineyes.ini file? (in the past this was suggested > for dealing with certain problematic programs such as total recorder)? > > Or, are you using a later version of VS than John was using (I think he's > using 2012)? > > I don't think it's correct to say that WE doesn't support UIA; it does, > using a MS mechanism where-by MS remaps UIA features into the MSAA > feature-set. My understanding is that UIA has more features, so you end up > only getting the info which MSAA could recognize, but this does work > (according to MS and GW), as far as I understand statements about this from > GW. > > Why don't you write directly to GW support about this? > > To answer at least one of your questions, no, you cannot preview a reclass > operation, but you can go back to the same control later and tell WE to > return the class to the original value if you don't like your reclass > results. > > Hth, > > Chip > > > -----Original Message----- > From: Rick Thomas [mailto:[email protected]] > Sent: Saturday, June 21, 2014 8:41 AM > To: [email protected] > 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 -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici [email protected]
