Rick, That's what I am suggesting: you should try to create an external app, probably using VS 2008, which will make VS 2013 accessible as its goal, because it can have access to UIA info. Surely you kept a copy or gave a copy of that project to someone? If not, you still have the experience, and it won't take you as long the second time.
Chip Whatever problems you had in the past, that was a very different version of WE; and I know they've listed several fixes since then, which were specific to problems experienced by external apps. -----Original Message----- From: Rick Thomas [mailto:[email protected]] Sent: Wednesday, March 25, 2015 2:59 PM To: 'Chip Orange'; 'Aaron Smith'; 'Window-Eyes Scripting List' Subject: RE: WEEvent and VS Conflict? Hi Chip: Back around 2010 or 2011 I created a vb.net script in vs 2008 for 2010 using vb.net for WE. I encorporated both the UIA model using the .net framework UIA Model and the WE Object Model in the script. There was a WE Keyboard method I could not get to work and after quite some time and allot of e-mail postings gave up on that scripting project as well - just ran out of time like now. A better approach might be to create an external script from scratch either in the .net platform or using something like python if going the UIA route. That project was on my old xp machine I gave to my brother in law and is likely long gone. Rick USA _______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
