Bug found and resolved in JAWS Script Exchange
- From: Jamal Mazrui <empower@xxxxxxxxx>
- To: jawsscripts@xxxxxxxxxxxxx, program-l@xxxxxxxxxxxxx, programmingblind@xxxxxxxxxxxxx
- Date: Thu, 18 Sep 2008 09:10:52 -0400 (EDT)
One of Doug Lee's hunches was right -- JSX code included a sorting problem
whereby "10" was not being recognized as grather than "5." A different
installation directory path is used for JAWS 5.x and below compared to
JAWS 6.x and above. I think I first created JSX when JAWS 6 was new.
Similar to a year 2000 problem, I evidently did not conceive of the JAWS
version getting up to 10! There has been a pattern of JAWS jumping major
version numbers with few increments, if any, within each major version, so
10 arrived much sooner than I conceived. Also, around JAWS 8 or so, a
registry change did result in JSX failing to find the right directory,
thus requiring some tweaking of its code, so I initially thought this was
another situation like that.
With that silly bug fixed, I have posted recompiled versions of the
following:
JAWS Script Exchange
http://EmpowermentZone.com/jsxsetup.exe
HomerKit
http://EmpowermentZone.com/kitsetup.exe
JAWS Scripts for Visual Studio 2005 or 2008
http://EmpowermentZone.com/msenv2005.exe
Besides the complete JSX distribution, itself, dates or version
numbers are not currently changed in the HomerKit or VS script
packages. I hope to incorporate other fixes or enhancements later.
Jamal
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
Other related posts:
- » Bug found and resolved in JAWS Script Exchange
