[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

w.r.t. calling display-force-output (re: trouble with CLX, LUCID,...)



i've got a call to XLIB::DISPLAY-FORCE-OUTPUT after each map-window and each
unmap-window call. i stuck them in there just to be trying "something". i will
be delighted to take them back out. however, this problem arose before i 
stuck them in there. and it still occurs, and in the same way and manner, as
when the code did not have them peppered through it.

the thing is dying, seemingly, after calls to xlib::create-<something>
functions; seemingly, either create-window or create-gcontext; when it does
die.
----------------------------------------------------------------------
      )     (
     /(_   _)\      Joshua Glasser
  )^\\_\-=-/_//^(   Artificial Intelligence Technologies, Incorporated
  /o (@)/.\(@) o\   40 Saw Mill River Road
  \/ ^__ ^ __^ \/   Hawthorne, New York 10532
     \|\VVV/|/      (914) 347 - 6860
      \\AAA//
       \~~~/    UUCP: uupsi!shadow!joshua or uupsi!ait.com!joshua
       ))|((    APRA: JOSHUA%AIT.COM@UU.PSI.COM