Moving objects and incremental redisplay

• To: SWM@stony-brook.scrc.symbolics.com
• Subject: Moving objects and incremental redisplay
• From: Brian Anderson 234-0878 <bha@ata.ca.boeing.com>
• Date: Wed, 29 Sep 93 11:01:25 PDT
• Cc: clim@BBN.COM
• In-Reply-To: Scott McKay's message of Tue, 28 Sep 1993 13:57 -0400 <19930928175757.9.SWM@SUMMER.SCRC.Symbolics.COM>

>     What is happening is that when I move an object, all the objects that
>     were drawn "after" the moved object are displaced an amount equivalent
>     to the displacement of the moved object.  That is, if I move an object
>     to the right, all objects that were drawn "after" the moved object are
>     also displaced to the right an equivalent amount.  Also, if I move an
>     object "over" another object, then move it off that object, the hidden
>     object's appearance is trashed.
> 
> Try supplying :FIXED-POSITION T in your calls to UPDATING-OUTPUT to see
> what happens.

This makes things work *much* better.  Now, everything appears in the
correct position after an object is moved.

But, I still have problems with overlapping output.  I tried the
clim:r-tree-output-history but this doesn't solve the problem.
Actually, the behavior does not seem to be noticably different between
the default output history and clim:r-tree-output-history.

ba

• Moving objects and incremental redisplay
• From: Scott McKay <SWM@stony-brook.scrc.symbolics.com>

• Moving objects and incremental redisplay
• From: Scott McKay <SWM@stony-brook.scrc.symbolics.com>

• Prev: tracking-pointer clauses?
• Next: Moving objects and incremental redisplay
• Index: CLIM Mailing list (1-Jan-93 to 31-May-94)
• Thread: CLIM Mailing list Index (1-Jan-93 to 31-May-94)