Ho, almost forgot, if you turn off automatic dynamic things in the IDE options you can still use then manually. That is you can use them by clicking what you want to do like check for syntax errors using the standard MenuBar selections - they just wont inturrupt you while trying to type or navigate around the ide - you just turn off the dynamic displaying of features and don't realy disable them. Also, if you want, and this gets a little complicated, you can script vb.net itself to read with WE better but again, this getstricky since you cant use vb.net to script vb.net (testing problems) without some fudging and I would recomment using something like c# to script vb.net and vb.net to script c#. That or use some other language like VBScript, Python or whatnot to script vb.net and then use vb.net to script all other applications if you want to go the vb.net route That said I think you can use vb.net to script vb.net if you make changes, create the exe and use the exe as a script over vb.net ty putting it into a script thingy for WE to use in place of the active exe in the project itself - said it might get complicated. but I don't think vb.net needs any scripting for most basic features - I do think scripting the forms designer would be a nice thing to do since WE wont work in it but I just turn on narrator when I want to get into the designer and turn it off when I move out of it. I find the most time consuming process is trying to analyze the tree structures of third party programs I want to script but that is the case with any language and independent of what scripting language you use. One other point is that in vb.net and other such external languages you can not only use the WindowEyes Object Model but you can use the managed UIA where the WE Object Model doesn't give you enough control or accessibility access to accessibility related UIA events. But guys, this is not a path raw beginners should tackle and it will be a lengthly process to slog through and I have only created one or 2 scripts and struggled every step of the way trying to get it done. But you can build on my experience and as you know the pros at GW have always been helpful whenever I got stuck. The same could be done for Python but I would be afraid of what Bruce mentioned about the third party developers and their modules and I have found it better to stay away from "Open Source" modules for just those reasons - many of them don't worry about accessibility and sop supporting their modules after they lose interest in their original projects. Rick USA
-----Original Message----- From: LBX [mailto:lab...@fltg.net] Sent: Friday, September 12, 2014 10:07 PM To: gw-scripting@gwmicro.com Subject: Re: VBScript Alternatives Hi! I will respond to this question in doing it for all. The intellisense has to be turned off. You can not run it for it changes the screen and Windoweyes does not like rapid dynamics, as if any program/app would. So when attempting to keep up it can even lock up. So you have to turn it off and not use it, that is the fix. In terms of other scripting languages, I was responding to the replacement only, along with Python brought up; since I wrote my games using it. The WX is the one I was talking about when attempting to get the writer to fix the issue and he could not. He was the one that wrote both WX and the Com modules for Python and I asked him if he could fix the issue and could not. In Python you have to use the MSVCrt module for keyboard events if you want display to work. Once in the video mode to get keyboard events, it stops talking and the screen is not readable....probably the same issue as WX has with it. I did get an imbedded WE or Sapi voice to get it to respond based on what was placed in the voice. So using Python you have to make the controls with the event running the voice object; that is the only way to read controls using WX Python. Let the voice inside the event do the talking for external scanning does not work. Rick try out the Python, learn it by writing a game. At least have some fun learning it. Time to sign out and get back to roofing again tomorrow... Bruce Sent: Friday, September 12, 2014 7:54 PM Subject: Re: VBScript Alternatives Hi. What did you do to Visual Studio 2013 to make it work? I am finding that intellisense does not work, and if I press tab it goes to some strange place and the end key goes to another file. I can certainly read the actual code. I am using c# rather than vb.net. What options did you change to make it work better with screen readers? Rick Thomas <ofbgm...@mi.rr.com> wrote: > Hi Bruce: > Visual Studio or any of the free modules have to be setup for accessibility > with a screen reader. > That said it works quite well once setup and the rather large learning curve > is mastered. > I use vb.net 2013 for Desktop with few problems with WindowEyes out of the > box except with the forms designer and the lack of support for reading line > numbers as in prior versions of Visual Studio related products. > After reading Aarons reply to this thread I am not sure this discussion is > worth much except where someone might want to learn another language for > their own personal use. > If he is correct and VBScript might be supported for many years to come > VBScript offers the general scriptor the best and most intuitive way to do > some app development. > Since I havent done much scripting recently I have no dog in this race > anyway. > If I create a app that doesn't require the use of the WE Object model I work > in vb.net for the most part. > If I end up working on something the WE Model I will consider my options at > that time. > Later and, again, congratulations on your project. > Rick USA > > -----Original Message----- > From: LBX [mailto:lab...@fltg.net] > Sent: Friday, September 12, 2014 10:14 AM > To: gw-scripting@gwmicro.com > Subject: Re: VBScript Alternatives > > Hi Rick, > > Yes, the .net I had taken 2 courses last year on them. The issues are > the readability of the menu's... > > The Python is OK but has reading an Issue using a screen reader. Modules > are version specific, based on what version of the C++ library and Windows > keeps changing it, so you have to be aware of it. > Now the based way to avoid them is keeping a stable version of Python > but modules are a pain when having to keep track of the version it was > compiled under. > > > The .net is OK to use, you also have to pay attention to what is focused > when inserting code and such. > > but if the WE module were to go to that, maybe we could end up with a > better reader for the .net menus which could make everyone happy. > > Chip had done this with the VBA and using the Word ability to list the > code choices. That would also be the way to go with the .net, having an easy > list of events and such to insert into the code at the cursor location and > such. > > Power Shell allows for the shell commands which is like Python and such, > but it is a way to go to get access to the Windows Com and such. But shell > has limitations in terms of display and screen events... > > If you get into Python, you will find it is an entirely different animal > and as you noted, indenting is a pain for screen reader programs unless you > turn on the space count feature, then you will get a lot more talking which > can end up being annoying. At least it would tell you how many spaces of > indent you have for Python, besides the arrow key movement when going up or > down; where blank lines mess up that ability to align things. > > So I think the .net is the way to go when Windows decides to get rid of > VbScript. For we as programmers could have easier usage of the C++ to write > apps with; making the code run much fast with less issues of timing and such > for events. > > Bruce > > > Sent: Friday, September 12, 2014 9:54 AM > Subject: RE: VBScript Alternatives > > > Hi Bruce: The 2 takeaways I got was that Python UI is not all that > accessible for screen reader users and that indentation is important which > is also a pain to track while programming for blind programmers. > Otherwise I am not a fan of "Open Source" modules since they tend to not > consider accessibility by most non visually impaired users and once a > developer creates a module they tend to stop support of the module over time > as they get involved in other things. > But, if Python supports com efficiently and the UI can be made very > accessible to screen reader users I don't see why it may not be a candidate. > Actually, I lean twoard the .net framework but that may just be my personal > background in it and based on my lack of deep knowledge of other languages I > don't know if there would be a better choice. > If GW goes in the .net direction we could put together some documentation, > some tutorials and perhaps, like Chip, some classes in learning to script > using whatever .net language was recommended IE vb.net, c# or C++ etc... > Rick USA > > > > --- > This email is free from viruses and malware because avast! Antivirus > protection is active. > http://www.avast.com > -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
