inferior-output-record-changed in 1.1

• To: suthers+@pitt.edu
• Subject: inferior-output-record-changed in 1.1
• From: Scott McKay <swm@harlequin.com>
• Date: Thu, 17 Mar 94 14:10:07 EST
• Cc: clim@BBN.COM
• In-Reply-To: Daniel D Suthers's message of Thu, 17 Mar 1994 11:35:00 -0500 (EST) <IhW8Oo68XZwy43c2lK@pitt.edu>

   Date: Thu, 17 Mar 1994 11:35:00 -0500 (EST)
   From: Daniel D Suthers <suthers+@pitt.edu>

   CLIM 1.1 (on Dec/Lucid, though that shouldn't matter):

   We don't understand how inferior-output-record-changed is supposed to work.

My counsel is to avoid trying to use this.  I think you will not
succeed -- and it's different in CLIM 2.0 as well.

   Specifically, why do you have to provide old-position and old-extent?
   These are already stored in the output record. The fact that they have
   to be provided as arguments suggests to us that we should have done
   something to modify the output record, thereby invalidating this
   information before inferior-output-record-changed gets called. 

   Could someone provide a template for the usual code pattern in which
   this is used? 

   thanks,

   --------------------------------------------------
    Dan Suthers           | LRDC, room 505A
    suthers+@pitt.edu     | 3939 O'Hara Street
    (412) 624-7036 office | University of Pittsburgh
    (412) 624-9149 fax    | Pittsburgh, PA 15260
   --------------------------------------------------

• inferior-output-record-changed in 1.1
• From: Daniel D Suthers <suthers+@pitt.edu>

• Prev: inferior-output-record-changed in 1.1
• Next: spreadsheets & clim
• Index: CLIM Mailing list (1-Jun-94 to 30-Jun-95)
• Thread: CLIM Mailing list Index (1-Jun-94 to 30-Jun-95)