[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

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

1852.0. "Documentation for XMultiplexInput()" by STKHLM::FEIST () Wed Dec 06 1989 04:25

    Hi
    
    Could anybody help me to find some documentation for the function
    XMultiplexInput()
    
     Regards Jonas Feist
    
T.RTitleUserPersonal
Name
DateLines
1852.1STAR::ORGOVANVince OrgovanWed Dec 06 1989 17:3814
    XMultiplexInput is an undocumented Xlib routine that allows a
    program to block until some input event occurs: either an event is 
    ready on a X11 display connection, or an event flag in cluster 0 is
    set, or a timer event occurs. The routine is only needed on VMS.
    
    I believe it was written solely to allow the toolkit to implement 
    XtAddInput. It's calling interface is not very clean, and we didn't
    document it so we could rework the interface later. 
    
    XMultiplexInput is only useful to VMS clients that are not using 
    the toolkit, since XtAddInput and other toolkit routines provide 
    equivalent functionality.
    
    Why do you think you need it?
1852.2XSelectAsyncEventCALL::SWEENEYThe Finite VoyageWed Dec 06 1989 20:529
    The toolkit (and XtAddInput) is the way to go to mix an asynch
    application environment with processing X events.
    
    But if you are not using the toolkit, then the clean method is to use
    the VMS supported and documented routines XSelectAsyncEvent or
    XSelectAsyncInput, they will call an AST routine when an event occurs.
    
    Your AST routine can set an event flag such that a blocked $WAITFR or
    other system service in your application will unblock.