Dear Michael: May I please point out that I ask as a user, and as a disability professional on behalf of thousands of existing users--to say nothing of yet more users who won't give Red Hat the time of day right now because of issues like this? Please pardon me if this sounds harsh, but the bug report is old. And, the submitted fix is also not new. And, the need is profound--though you will not see it on a monitor. You must listen to a speech synthesizer read out the screen (or read the dots on a refreshable braille display screen) to observe the glaring problem: Now, I happen to know that Red Hat has a capable hardware speech synthesizer at its disposal, because I personally provided it free of charge for testing purposes over a year ago. Why a company with millions in annual revenue couldn't come up with $300 for a simple computer part is something I have not previously questioned. I simply provided the part. So, let me question the issue at hand. Has the fix been tested? What is the report? If there's a problem, wouldn't you agree we're entitled to know about it? And, if there isn't a problem, shouldn't the fix be in? Again, I apologize for my strident tone. I am simply unwilling to hear this fix didn't make the cut for the next release. To my mind that would be unconsionable on Red Hat's part given the circumstances. So, one more time, what's been done vis a vis this bug report? Michael K. Johnson writes: > From: "Michael K. Johnson" <johnsonm@xxxxxxxxxx> > > Because this is a development issue, please followup to rhl-devel-list. > > On Thu, Aug 07, 2003 at 01:51:06PM -0400, Janina Sajka wrote: > > The cursor tracking problem first reported against newt well over a year > > ago, and recently re-opened as the community of blind users tracked down > > the problem and created the resolution patch, continues unresolved as > > shown by Bugzilla just a few moments ago. May I point out that this fix > > is extremely important to thousands of users of Speakup worldwide? > > > > So, is there a problem with the fix submitted? It would be most helpful > > to have newt working properly in Cambridge. > > The problem is, I think, reviewing it to make sure that it doesn't break > anything else. A description of exactly why the change is a fix can help > for things like this. > > - newtGotorc(co->top + (li->currItem - li->startShowItem) + 1, co->left + 1);+ newtGotorc(co->top + (li->currItem - li->startShowItem) + li->bdyAdjust, > + co->left + li->bdxAdjust); > > I note that bdxAdjust is set only to 0 or 2, and it's not at all clear > to me how changing bdxAdjust applies to this bug report from the > description. It might still be correct or an improvement, but it is > not clear at a short read why it is either. > > The change to bdyAdjust makes sense to me as a fix for this bug report. > > michaelkjohnson > > "He that composes himself is wiser than he that composes a book." > Linux Application Development -- Ben Franklin > http://people.redhat.com/johnsonm/lad/ > > > -- > Rhl-list mailing list > Rhl-list@xxxxxxxxxx > http://www.redhat.com/mailman/listinfo/rhl-list -- Janina Sajka, Director Technology Research and Development Governmental Relations Group American Foundation for the Blind (AFB) Email: janina@xxxxxxx Phone: (202) 408-8175
