[blindreplay] Re: Attention Window-Eyes 6.1: Feedback needed

  • From: "Rick Alfaro" <rick.alfaro@xxxxxxxxx>
  • To: <blindreplay@xxxxxxxxxxxxx>
  • Date: Thu, 3 Apr 2008 13:37:05 -0400

Hi.

FYI, delays as specified in the WE control panel in either general/cursor
delay or in any of the cursoring key definitions have no affect when using
the arrow keys in menus, context menus, or listviews.  You can bring the
values all the way up to 99 and it will not make any difference.

I am pretty sure that the issue here may be that Applian is using owner
drawn menus in which case WE has to rely on its OSM.  It's possible that GW
might be able to work around it at some point, but I believe the true fix
would be if Applian would use the screen reader present flag and use a
standard menu if a screen reader is present.  Either that or make it an
option under settings. Using the screen reader present flag would be a much
more elegant approach though.

Of course, this is just an educated guess on my part.



Warmest regards,
 
Rick Alfaro
rick.alfaro@xxxxxxxxx


-----Original Message-----
From: blindreplay-bounce@xxxxxxxxxxxxx
[mailto:blindreplay-bounce@xxxxxxxxxxxxx] On Behalf Of rs_denis
Sent: Thursday, April 03, 2008 10:05 AM
To: blindreplay@xxxxxxxxxxxxx
Subject: [blindreplay] Re: Attention Window-Eyes 6.1: Feedback needed

    The initial changes I made to try to get the menus back in sync with 
window eyes were minimal adjustment in cursor delay.  This has not worked at

this point but I have not tried more than one new setting so far.  I am also

thinking that the main screen may need to be reclassed or the fields may 
need to be redefined to get everything properly sorted.  I have a suspicion 
that whatever the resize handle option does contributes to this problem.  I 
tried using it to move or alter the shape of the window without success. 
Something is giving the menu header one reading but the cursor and arrows 
are off by one menu item.  I will continue looking into possible adjustments

to the basic window eyes sets as time and energy permit.  It's not high 
priority for me since I didn't know there was a problem till it was pointed 
out here.  I've been using replay products since replay radio 4.xx so have 
just not taken the long route in doing things in later versions.  As 
mentioned sometime in the past, I still use replay radio 7.xx for some tasks

because it does what I want comfortably.
Ron Denis 

--
To unsubscribe: e-mail blindreplay-request@xxxxxxxxxxxxx with unsubscribe in
subject
To contact list owner: e-mail blindreplay-admins@xxxxxxxxxxxxx

--
To unsubscribe: e-mail blindreplay-request@xxxxxxxxxxxxx with unsubscribe in 
subject
To contact list owner: e-mail blindreplay-admins@xxxxxxxxxxxxx

Other related posts: