Hi Eileen, The URL is near the top of my message below <smile>, and restated here http://www.EmpowermentZone.com/edsetup.exe FYI -- Inthane's Grab Bag site has descriptions and links to almost all programs I have developed http://GrabBag.AlacornComputer.com Thanks for your interest, and for any reporting you can do with FS. Cheers, Jamal On Mon, 19 Nov 2007, Eileen Lafond wrote: > Date: Mon, 19 Nov 2007 11:32:09 -0800 > From: Eileen Lafond <Eileen.Lafond@xxxxxxxxxxx> > Reply-To: programmingblind@xxxxxxxxxxxxx > To: programmingblind@xxxxxxxxxxxxx > Subject: Re: SayAll in EdSharp with JAWS 9 beta > > Hi, Jamal, > Where do I go to download Ed Sharp? > > Thanks, > > Eileen La Fond > Phone (206) 386-0011 > e.mail Eileen.LaFond@xxxxxxxxxxx > > >>> Jamal Mazrui <empower@xxxxxxxxx> 11/17/2007 4:03 AM >>> > As you may know, EdSharp > http://www.EmpowermentZone.com/edsetup.exe > is an editor that attempts to maximize productivity by screen reader > users, levering the best of my programming skills and experience so far. > EdSharp is a text editor, word processor, HTML writer, coding environment, > and file converter, developed in the C# language and based on the .NET 2.0 > Framework. JAWS 9, which many of us use, is in public beta, so this is an > opportune time to make a difference in its development. > > With the current version, I encountered a problem that's quite concerning. > It happened with a previous JAWS beta once before, and I was hoping that > improved stability since then would have eliminated it in the latest beta. > Not so, unfortunately. > > A SayAll in a large file (not huge, about 1 meg) seemed to be going > fine. After a few pages, EdSharp stopped. I tried to examine the text, > thinking there might be a lot of white space that confused JAWS. JAWS > would not respond with SayLine or any other key. Instead, the text > seemed to continue scrolling without speech. I tried Control+Home to > get back to the top of the document, but this did not work either. I > Alt+Tabbed away and then returned, but still the same problem. > > Eventually, after working in another application, I returned to EdSharp > and found JAWS responsive to commands there. Not surprisingly, I had > lost my place. When I found it via a search, however, I did not find > anything unusual in the document at the point where the SayAll went > crazy. > > If you get a chance, I'm curious whether this happens to you. It may > not happen until after a few screens of reading, so pick something that > you'd find useful reading anyway! If you experience a similar problem, > please try to report it ASAP via the JAWS beta report form at > http://www.freedomscientific.com/fs_support/jawsbetareport.asp > > Rumors are that Freedom Scientific is getting ready to release the > official JAWS 9.0, and I really want long standing issues with SayAll in > large documents to be fixed. I have reported them myself, but every voice > helps, particularly so that Freedom Scientific knows there are JAWS users > of a product besides its developer! > > Another SayAll problem is noticeable when JAWS is set to "read by line > without pauses" in the EdSharp.jcf configuration file. This is the > default setting for JAWS SayAll, but a user alerted me to the fact that > JAWS repeats text in a large document. Accordingly, I have made "read by > sentence" the current setting in EdSharp.jcf, but that is not optimal for > other reasons, including the apparent instability mentioned above. To > check whether reading by line causes repeated text for you, go to the > SayAll options dialog in JAWS configuration Manager. > > Unfortunately, other SayAll issues remain with TextPal > http://www.EmpowermentZone.com/palsetup.exe > where JAWS either fails to start reading or has long pauses in a SayAll of > a large document. > > Thanks for whatever you can do to advocate with Freedom Scientific > about this and any other compatibility issues you may have discovered > with applications I have developed. They are meant to maximize > productivity by blind users, and there are limits to what I can do > without reasonable cooperation by the major screen readers. Getting > JAWS to behave properly with common Windows controls used by these > applications should help improve JAWS generally. By design, I avoid > unusual, custom controls and generally try to accomplish all user > interface interaction with common ones that should be well understood > by screen readers, especially since they implement Microsoft Active > Accessibility. > > Regards, > Jamal > __________ > View the list's information and change your settings at > //www.freelists.org/list/programmingblind > > > __________ > View the list's information and change your settings at > //www.freelists.org/list/programmingblind > __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind