I would argue that standard, main stream languages such as VB, VB Script, C++ or what have you are much more tried and tested than the jaws scripting language, not to mention much more powerful. But I'm just an entry level computer science major. Grin I don't think that scripting inherently makes Window-Eyes less stable. A poorly written script can definitely reek all kinds of havoc, but the scripting engine itself I would say has very little to do with instability issues. There are also other factors. You could have a perfectly written script (if there is such a thing) but if it is trying to interact with a com control or other external program that is buggy, that can also lead to instability. It could look like it is the script that is buggy when in fact it is the com interface for that particular program. This is not to say that scripts and script writers are not the culprit in certain situations, but I would hesitate to jump to such a conclusion right away, because there are lots of factors that come into play here.
-----Original Message----- From: Chris Hill [mailto:[email protected]] Sent: Sunday, July 05, 2009 9:55 AM To: [email protected] Subject: Re: Well, I guess not after all I suspect you're right. Frankly, the only scripts I'm using here are the progress indicator and the autocomplete. I could live without those, and I had scripting turned off in 7.01 for months and didn't realize it. Jfw may have a better idea using their own language rather than the window-eyes approach of allowing low level access with multiple languages. It all depends on how stable these interfaces really are. Time will tell which method is going to work out the best, and whether or not more has been bitten off than can be chewed. On Sun, 05 Jul 2009 08:41:06 -0500, you wrote: >Well Chip, I certainly am not the techie that you are, but I've >wondered for a while, especially since scripts were introduced in WE, >if scripting doesn't inherently contribute to instability of screen >readers generally. I mean, is it possible that even the fish wouldn't >be a bit more stable without them? Hey, don't get me wrong, I really >like the convenience of scripts. They really do make things more >convenient, and even make things possible that wouldn't be otherwise >with certain applications, but I'm wondering if one of the side >effects isn't unstable or unpredictable behavior that can only be >explained by an active scripting engine. Now understand, I'm not >making a declaration, just posing a question. And even if what I >suspect is in deed true, would any of us want to go back to life >without them. > >I will probably have to do the tear down build up routine with the >scripts to eventually get to the bottom of this one, and I'm not even >sure that will be the answer because I was really under the >impression that getting rid of the detect shortcut keys script had >been the culprit, and even provided myself with a logical explanation >as to why this might be. I thought that maybe the use of the >ctrl-shift-r keys might possibly be interrupted by that particular >script in order to determine if that key combination might represent >a shortcut of some kind. At least, that is what I would think that >might be the function of that script, simply judging by its stated on >its face purpose. Anyway, this little project will give me a little >bit more to do with my time, although I can think of better things ><g>. Anyway, I really do appreciate your input on this matter. > >Thanks much, > >Larry > > > >At 12:26 PM 7/4/2009, you wrote: >>Hi Larry, >> >>I want you to know I'm having my own issue, nothing to do with firefox, but >>it acts just like yours. it stopped happening when I disabled scripting, >>and when I enabled the scripts one by one, it never came back. >> >>this happened after an embarassing episode where I wrote a demonstration >>script which caused it to happen on my vista pc and sent it to GW, who of >>course did not see it happen, but I think they got a little irritated with >>me. >> >>still, there's something about running scripts, which can seem to make >>things go wrong, without it seeming to be any particular script. >> >>Chip >> >> >> >>-----Original Message----- >>From: Larry Higgins [mailto:[email protected]] >>Sent: Saturday, July 04, 2009 10:51 AM >>To: [email protected] >>Subject: Well, I guess not after all >> >>OK, the latest is as follows. I thought I had solved the problem by >>unloading that detect shortcut script, but when I restarted Firefox, the >>problems returned. I immediately went back to the script menu and turned off >>scripts, and everything returned to normal. Then I turned scripts back on, >>and everything still continued to function normally. >>Looks like I'll have to continue to go through this little ritual every time >>I want to run Firefox, that is unless any of you can possibly determine >>logically from my description of the problem just what might be the >>alternative. Oh well, I guess it was just too good to be true. >> >>Larry >> >>If you reply to this message it will be delivered to the original sender >>only. If your reply would benefit others on the list and your message is >>related to GW Micro, then please consider sending your message to >>[email protected] so the entire list will receive it. >> >>All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can >>be searched through and sorted using the search form at the bottom of the >>page. >> >>If you wish to unsubscribe from this list, send a message to >>[email protected] and include leave gw-info in the body of the message. >> >>If you reply to this message it will be delivered to the original >>sender only. If your reply would benefit others on the list and >>your message is related to GW Micro, then please consider sending >>your message to [email protected] so the entire list will receive it. >> >>All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, >>and can be searched through and sorted using the search >>form at the bottom of the page. >> >>If you wish to unsubscribe from this list, send a message to >>[email protected] and include leave gw-info in the body >>of the message. >> >> >>__________ Information from ESET NOD32 Antivirus, version of virus >>signature database 4217 (20090704) __________ >> >>The message was checked by ESET NOD32 Antivirus. >> >>http://www.eset.com > > >If you reply to this message it will be delivered to the original >sender only. If your reply would benefit others on the list and >your message is related to GW Micro, then please consider sending >your message to [email protected] so the entire list will receive it. > >All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search >form at the bottom of the page. > >If you wish to unsubscribe from this list, send a message to >[email protected] and include leave gw-info in the body >of the message. > If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search form at the bottom of the page. If you wish to unsubscribe from this list, send a message to [email protected] and include leave gw-info in the body of the message. __________ Information from ESET NOD32 Antivirus, version of virus signature database 4218 (20090705) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4218 (20090705) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search form at the bottom of the page. If you wish to unsubscribe from this list, send a message to [email protected] and include leave gw-info in the body of the message.
