| 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 |
Hellow,
I have again a similar question like in BULOVA::DECWINDOWS Note 1301:
A customer ports his geomapping product on our workstations under VMS/DECwin-
dows. So far everything is ok, there remains one problem:
He wants to use the digitizing tablet on a asynch board directly at the
workstation/terminalserver and get a X11-event everytime the tablet is used:
X11-standard does not support events from the the asych port for this purposes.
My question:
1) there seems to be a solution with XtAddInput and some AST- programming.
Do you have experience? Do you have a programming example? If not, do you
have any pointers...?
I allready got a demo-programm addinput.c (rsp .uil) which shows a solution,
but does not drive directly an asynch-port.
2) There seems to be a solution with a second X11-client, controlling the asych-
port and then communicating with the main X11-client, which handels the main
interface on the screen. Same questions as under 1)...
4) Are there allready known other solutions for this kind of problem?
The customer comes from a HP/UNIX-environment and says, that the XtAddInput-
Handling would be much easier in the UNIX-env. Thats why I still look for
other solutions.
Thanks a lot
peter trachsel, dec bern switzerland
(
for mail:
bern01::trachsel 48.240
bern02::trachsel 48.239 )
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1836.1 | More than one answer | SDSVAX::SWEENEY | The Finite Voyage | Mon Dec 04 1989 08:43 | 26 |
Peter, you've asked more than one question, contradicting yourself.
The first thing to understand is that "events" are ususally "server
events". "Client events" are not an attempt to create an RPC, but
implementors and hackers use them that way in any case.
Supporting a digitizing tablet on an asynch line could be implemented
as a server's source of input events, just like the mouse and keyboard.
This is elegant and difficult but not impossible. You need
documentation on the server, and I don't recall who the source is for
that now.
Easier to implement, is to create an application to allow the asynch
board a client source of events. If this is a separate process, you'll
need some method of identifying the digitizer source and the client
application destination "windows".
In either case, there plenty of event codes that are unallocated that
you case use. X supports such extensions.
That was X, "XtAddInput" is the toolkit intrinsics. Examples for
XtAddInput exist (I think I even wrote one of them), except that the
system hosting the conference, ELKTRA has some problem with Notes right
now. You would use XtAddInput to combine the input of X with the QIO
world of the digitizer. Just like I use XtAddInput to combine the
input of the X world with the DECNET task-to-task world.
| |||||
| 1836.2 | See the DW Device Driver Manual | STAR::ORGOVAN | Vince Orgovan | Mon Dec 04 1989 18:08 | 4 |
Customers can add support for asynch boards with digitizing tablets
by writing a DECwindows device driver. Documentation for doing it
is provided with the DECwindows programming kit: VMS DECwindows
Device Driver Manual, order number AA-MG28A-TE.
| |||||