I'm on my way to being a scripter due to my acquaintance with the .net framework and the C# language. But until then, thanks. And if It's UIA that the program uses (WPF UI), what then?
From: Chip Orange [mailto:[email protected]] Sent: Saturday, November 26, 2011 7:35 PM To: [email protected] Subject: RE: how to know what to reclass controls as when encountered Hi Katherine, I'm afraid you can't reclass unless you have a pretty good idea as to what it should be. If you're a scripter, you can use the various scripting tools to take a look at the control's name or class (which often gives you a hint as to what it's being used for), or the MSAA info log using the WE Event app might tell you something. If you're not a scripter, then you are usually left to trial and error (and a lot of the time, you have to set it back to "original" because whatever you chose is worse than what it was doing). Sorry it's not easier than that, but if it is, I'm afraid I don't know about it. Chip ________________________________ From: Katherine Moss [mailto:[email protected]]<mailto:[mailto:[email protected]]> Sent: Saturday, November 26, 2011 7:19 PM To: [email protected]<mailto:[email protected]> Subject: how to know what to reclass controls as when encountered Hello all, I was fooling around a few weeks ago with the WCF service configuration editor (a tool in the Windows SDK that I will need in future development endeavors), and I realized that some of the controls were custom according to WE, so I made an attempt at reclassing them. I reclassed them as buttons not knowing what they were actually supposed to be, and whatever I did, that seemed to make them all disjunct and unreadable. WE could read them, but it sounded like Gibberish rather than English. What is the first step when trying to reclass a control in figuring out what it should be? Thanks guys. Katherine Moss, Administrator of the AccessCop Network, previously Raeder24.org. Visit us on the web at http://raeder24.org<http://raeder24.org/>
