Hi Rick, Let me make sure you are aware that the Fruit Basket script I posted is different from the GW sample on the web. They are similar, and I think we have learned from and incorporated parts of each other's work on this project.
I just posted a 1.4 update to mine (available via the Install Packages script or however you get packages), which automatically is associated as a global script. Once installed, you can press Control-Shift-F8 to invoke the dialog. It is intended to illustrate how VBNET can be used to create a Window-Eyes script (either global or application), including registering a hotkey, implementing a wescriptui dialog, and responding to a shutdown event from Window-Eyes. Although .NET Windows Forms could also be used, I think wescriptui dialogs are even easier to create (either way is OK though). I know you think of me as a "bits and bytes" kind of a programmer, and I appreciate that you think I have such low-level knowledge. I would characterize myself as more of a middle and upper level programmer, who prefers dynamic languages for rapid application development, but will learn enough low level detail when a higher level routine is not available. I do not know C++, which is the leading low-level language of today. I respectfully disagree with an opinion you have expressed that Visual Studio is more productive with .NET languages than a text editor and command-line compiler. I have seen message after message from you over the years as you have struggled to get VS to behave in a screen reader-friendly fashion. Of course, I do not know this for sure, but would guess that that the costs of using such a complex, visually-oriented IDE have outweighed the benefits you could have obtained from learning the language syntax without IntelliSense (certainly a convenience) and manually coding just what you need, rather than having to deal with lots of generated, template-driven code, much of which is extraneous to the particular task at hand. Consider the fruit basket program as an example. GW has posted a VS project containing multiple files and subdirectories. You are experienced with VS, yet still have not found a way to get it to work for yourself. The example I posted, on the other hand, is a single source code file, FruitBasket.vb, compiled easily at the command-line with a batch file, CompileFruitBasket.bat. Any errors are displayed on the screen and accessible during the debugging process (no fighting with the VS error window, for example). No variables or routines are automatically created that are not relevant to the task at hand. The entire program can be understood by reading one file from top to bottom. Global searches and replaces are easily possible in that single file. This is meant as a helpful, alternative perspective to consider. Let me know if you have any questions. Best, Jamal On Thu, 16 Jul 2009, RicksPlace wrote: > Date: Thu, 16 Jul 2009 11:04:23 -0400 > From: RicksPlace <[email protected]> > Reply-To: [email protected] > To: [email protected] > Subject: Re: Fruit basket sample using Visual Basic .NET > > Thanks: I might try that. So, it has to be loaded as a global script, ok, > I'll remember that. > Rick > ----- Original Message ----- > From: "Aaron Smith" <[email protected]> > To: <[email protected]> > Sent: Thursday, July 16, 2009 8:44 AM > Subject: Re: Fruit basket sample using Visual Basic .NET > > > > On 7/14/2009 9:40 PM, RicksPlace wrote: > >> I tried to execute it but got the Microsoft Message that it encountered a > >> problem and asked me if I wanted > >> to send it to Microsoft. > > > > I said this before before, but I'll do it again here, as it seems you may > > have missed my first reply: you have to load the resulting exe as a global > > script in Window-Eyes; it is not a stand alone application, but rather an > > external script. > > > > And, for the record, I was able to compile and run this example > > successfully. > > > > Aaron > > > > -- > > To insure that you receive proper support, please include all past > > correspondence (where applicable), and any relevant information > > pertinent to your situation when submitting a problem report to the GW > > Micro Technical Support Team. > > > > Aaron Smith > > GW Micro > > Phone: 260/489-3671 > > Fax: 260/489-2608 > > WWW: http://www.gwmicro.com > > FTP: ftp://ftp.gwmicro.com > > Technical Support & Web Development >
