[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
Moderator: | STAR::VATNE |
|
Created: | Mon Oct 30 1989 |
Last Modified: | Mon Dec 31 1990 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3726 |
Total number of notes: | 19516 |
2086.0. "DECW appl. & blind users" by TOWNS::WURZBERGER (Ron Wurzberger) Fri Jan 19 1990 12:40
I have a customer that has a DECwindows application that needs to be
modified for use by blind users; obviously, use of the mouse is
inappropriate. The application currently uses the standard mainloop
routine. The customer would like to provide some text input area,
either a command field or a DECterm window, so the blind user can enter
commands that would cause the application to operate as it would for a
sighted user. The application would run continuously throughout the
day although any number of users may use it during the day. When the
blind user uses the application, the displays must be updated to
reflect any changes the user has made so that when the next sighted
user sits down to use it the screen is valid - meaning scale and scroll
pointer values, text regions, and graphics displays must be updated to
reflect current values in the application even though the DECwindows
interface was not used to change them. If the customer uses a DECterm
window for input, no callback will be available to update the displays.
How can the application make visible those changes made via setargs,
setvalues, and other means from the mainline program as opposed to a
callback routine?
thanks,
Ron
T.R | Title | User | Personal Name | Date | Lines
|
---|