Xref: utzoo comp.os.vms:37229 comp.windows.x:34503
Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!rpi!usc!apple!agate!agate!jym
From: jym@mica.berkeley.edu (Jym Dyer)
Newsgroups: comp.os.vms,comp.windows.x
Subject: XtAppAddInput() on VMS---A Different Approach?
Message-ID: <JYM.91Mar25171930@remarque.berkeley.edu>
Date: 26 Mar 91 01:19:30 GMT
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Organization: Berserkeley
Lines: 24

___
 __ A few months ago I appealed to these newsgroups for help using
  _ XtAppAddInput() with mailbox input under VMS.  The exchange of
    messages that followed led to a solution:

	o Use an EFN in cluster 0.  And a separate IOSB.
	o Use $QIO and IO$_WRITEATTN to queue up a AST demon
	  routine which is called when something is written
	  to the mailbox.
	o Have the demon routine explicitly set the EFN and
	  set the status in the IOSB to 1, thereby telling
	  the DECwindows event loop that it's got something
	  to deal with.
___
 __ Well, somebody in my department has written a little package
  _ that does mailbox IO a bit differently.  It queues an asynch-
    ronous read request to the input mailbox at appropriate
    times.
___
 __ It seems to me that if I use this package, I'll probably have
  _ a simpler technique overall.  Has anyone implemented anything
    with DECwindows that works this way?  If so, could you tell me
    any pitfalls and such I might watch out for?
    <_Jym_>