Conference bulova::decw_jan-89_to_nov-90

1918.0. "X Default Error Handler calling condition handlers?" by DDIF::MCEVOY () Thu Dec 14 1989 12:02

    I've noticed the following behavior on VMS Xlib 5.3;
    
    If I set up a condition handler outside of my XtMainLoop,
    and I then have a call which generates an X error within
    my code, the default X error handler is called, and then
    my condition handler is called; and my routine which generates
    the X error is not re-entered because the condition handler
    is established at the main application level.
    
    If I do not have a condition handler set up, then the routine
    will generate the x error, and then continue along processing.
    
    To me, this seems like the correct behavior in either case;
    I don't think the default X error handler should be looking for
    a condition handler and calling it if there is one in effect;
    
    Wouldn't this require me to set up a condition handler around every
    X call that might generate an X error (most of them) if I want to 
    also have a generic condition handler outside my XtMainLoop()?
    
    Any info on exactly how this works on VMS would be much appriciated.
    
    thanks -dennis
                 

    discussion moved to DECWINDOWS_PROGRAMMING conference.