Hi Kate and Chip: I had heard that also. For the Pro and above you can use plug-ins and I guess there is more of a DOM available. I was hoping to be able to use the existing DOM and MSAA in the Express versions to clean up some of the less user friendly features. I just am not going to drop hundreds of dollars just to create scripts, if they can be created for WE, when I use the Express versions. I can work around the problems manually for the most part but would prefer a clean IDE with things all working properly if possible. Well, I am waiting for the final release version of VS 11 to see how it handles the new features like that Metro stuff. By the way, MS has deprecated support for Macros in VS 11 if not in 2010 since they said less than 1 percent of their clients use that feature. I wonder what percent of their clients use UIA and ARIA accessibility hooks? Anyway, it is what it is so I'll close this thread with a big thank you to you folks. I have a VB.net script working so if anyone ever wants it as a base to build from let me know. It is in vb.net 2008 express so will likely be out of date sooner rather than later but at least I finally have it working thanks to some clean base code from Aaron. Thanks Aaron, if you are reading this and good work you old guru. Later: Rick USA ----- Original Message ----- From: Katherine Moss To: [email protected] Sent: Wednesday, April 25, 2012 3:31 PM Subject: RE: WE And Microsoft Development Environments
You're thinking of the professional version, I think. Pro or above has the object model. From: Chip Orange [mailto:[email protected]] Sent: Wednesday, April 25, 2012 2:21 PM To: [email protected] Subject: RE: WE And Microsoft Development Environments Hi Rick, Well, the other approach is to see if you can get info from any object model (I thought I had read that VS (premium, maybe not express) does have one, and then there's the window native object model to investigate). I suspect VS is using UIA, and that's why you're seeing garbled text, and not much of it. I understand it still has several bugs everyone is waiting on MS to fix. I would stay with VS 2008 for now if none of the alternatives above works out. Chip ---------------------------------------------------------------------------- From: RicksPlace [mailto:[email protected]] Sent: Wednesday, April 25, 2012 8:16 AM To: [email protected] Subject: Re: WE And Microsoft Development Environments Hi Chip et al: In Visual Studio 2010 the Forms Designer uses something called Adorners. These appear to be WPF based and I can't get anything out of them using the WE Immediate Window Analysis tool. I would create a project, open the Forms Designer and drop some controls on it like a TextBox and buttons. I can not get to them using the cursor at all and can get to them with the Mouse but often the text is garbled when reading with the mouse. I was going to script the window but haven't been able to use the GW WE Immediate Window Tool to get at the buttons, text boxes etc... within the window. I have tried using the Print Mouse.xxxxx in many combinations with no luck. I even tried using WeEvent but it does not tell me anything about the button, textbox etc... controls either. Have you guys run up aginst these window types and how did you get at their children? Note that I get the Adorn window info but it says it has no children so that doesn't seem to work either. I remember getting the clips but there were 11 clips, they were jumbled up and researching I found that this type of control may be using glyphs, not sure. Does this type of control exist in other MS software like Word etc... Any ideas I might try to get at these controls? Rick USA ----- Original Message ----- From: Chip Orange To: [email protected] Sent: Sunday, April 22, 2012 5:14 PM Subject: RE: WE And Microsoft Development Environments Hi Rick and Kate, Don't forget the best place for scripting tutorials and articles is the GW wiki at: http://gwmicro.com/wiki Just create an account there, take 15 mins to read the article on basic formatting of wiki text, and then create your new article page. The great thing about putting stuff here, aside from there's already this great collection and we'd like to keep everything in one spot if possible, is that anyone can add more to any article to flesh it out, make corrections, link it to associated resources they have found, etc. Also, there's an associated wiki page behind the scenes for each article where we can discuss ideas and suggestions for how the article might be modified or otherwise improved. Chip ------------------------------------------------------------------------ From: Katherine Moss [mailto:[email protected]] Sent: Saturday, April 14, 2012 6:06 PM To: [email protected] Subject: RE: WE And Microsoft Development Environments You can have a place on my site. After all, my site is a technology site as well. From: RicksPlace [mailto:[email protected]] Sent: Saturday, April 14, 2012 3:44 PM To: [email protected] Subject: Re: WE And Microsoft Development Environments Hi Kate: Well, have a hot key working and the MSAA stuff working and next up will be a simple Window Hook to display the Properties related to a Window or Window Control. Then I will write up the step by step and... I will make them available to wherever, doesnt matter. What would be good is an index of links with pages of tutorials online but I dont want to spend the time to build that. I will see if there is a way to have tutorials linked to from App "Central but I will likely give them to Chip to add to his current Scripting tutorial series as I did with the Globalization Tutorial. I have not done much with Windoweyes nor scripting in some time now so am not familiar with where things are located but can usually find them if I need them. Later Kate and have a good weekend. Rick USA ----- Original Message ----- From: Katherine Moss To: [email protected] Sent: Saturday, April 14, 2012 1:11 PM Subject: RE: WE And Microsoft Development Environments You should post them to app central where we all can see them! That would be nice for those of us .NET junkies over here LOL. Because I'm sure that I'm not the only one who is. From: RicksPlace [mailto:[email protected]] Sent: Saturday, April 14, 2012 5:01 AM To: [email protected] Subject: Re: WE And Microsoft Development Environments Hi Aaron. Thanks again and I will continue experimenting with it today. My old Script (App) defined (Registered) a Hot Key that worked and I think accessed a Window Object's Properties and Events. If these work that will demo: Use of MSAA; Use of a Window Object; Use of a Hot Key. That should make for a pretty decent intro demo and tutorial to post up someplace. I will likely continue with a second Demo and Tutorial with a few more features after this one. So far so good. Rick USA ----- Original Message ----- From: Aaron Smith To: [email protected] Sent: Friday, April 13, 2012 8:35 PM Subject: Re: WE And Microsoft Development Environments On 4/13/2012 5:19 PM, RicksPlace wrote: It still needs some testing and the Form1 grabs focus sometimes even though hidden. You can keep the form from displaying by creating a Main() routine, and putting your startup logic there: Sub Main() ' Instantiate your form Dim myForm as Form1 = New Form1() ' Put initialization stuff here instead of in Form_OnLoad ' Continue on without displaying the form Application.Run()End SubIf you then ever need to show the form, you can do myForm.Show() You can do this in C#, too, by changing code in the Main() function in Program.cs from: Application.Run(new Form1()); to Form myForm = new Form1(); Application.Run(); Aaron -- Aaron Smith Web Development * App Development * Product Support SpecialistGW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825260-489-3671 * gwmicro.com To insure that you receive proper support, please include all pastcorrespondence (where applicable), and any relevant informationpertinent to your situation when submitting a problem report to the GWMicro Technical Support Team.
