Re: Repairing damaged application panes

• To: pkarp@Sunset.AI.SRI.COM, York@lucid.com
• Subject: Re: Repairing damaged application panes
• From: Scott McKay <SWM@stony-brook.scrc.symbolics.com>
• Date: Wed, 26 Aug 1992 10:21-0400
• Cc: SWM@stony-brook.scrc.symbolics.com, halverson@crd.ge.com, clim@BBN.COM
• In-Reply-To: <CMM.0.90.2.714782063.pkarp@Rockaway.AI.SRI.COM>

    Date: Tue, 25 Aug 1992 18:34 EDT
    From: Peter Karp <pkarp@ai.sri.com>

    I would like to argue for a mechanism that allows repair of damaged
    panes, that is independent of the event loop.  People here complain
    that if an application prompts the user with a menu, then computes
    for a while, then goes back to the event loop, that a damaged region
    persists during that computation and looks ugly.  If you know a large
    amount of computation is about to occur, it would be nice if you
    could force repairs to occur.

Call REDISPLAY-FRAME-PANE, or (in CLIM 2.0) REPAINT-SHEET.

• Re: Repairing damaged application panes
• From: kanderso@BBN.COM

• Re: Repairing damaged application panes
• From: Peter Karp <pkarp>

• Prev: selective accepts
• Next: selective accept
• Index: CLIM Mailing list (1-Jan-92 to 31-Aug-92)
• Thread: CLIM Mailing list Index (1-Jan-92 to 31-Aug-92)