Re: problems with 1.1 output records under incremental redisplay

• To: Scott McKay <swm@harlequin.com>
• Subject: Re: problems with 1.1 output records under incremental redisplay
• From: Daniel D Suthers <suthers+@pitt.edu>
• Date: Tue, 15 Feb 1994 17:26:43 -0500 (EST)
• Cc: clim-support@lucid.com, clim@BBN.COM
• In-Reply-To: <5727.9402142236@tigris.harlequin.com>
• References: <5727.9402142236@tigris.harlequin.com>

>    When we call clim:draw-text with :start and :end to write a portion of
>    a string, the output record that is created is too long (according to
>    my programmer, long enough to include the entire string). That is,
>    selectable regions overflow far to the right. Does draw-text* ignore
>    :start and :end in deciding how big the output record should be?
> 
> I didn't try this, since I don't have CLIM loaded right now.

My programmer (Massimo Paolucci) reports that when he copies the
substring and then calls draw-text* on the entire substring rather than
using :start and :end on the original string, the oversized record
problem goes away.  Seems like pretty strong evidence. 

So we will copy all our substrings until we hear from Lucid. 

--------------------------------------------------
 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
--------------------------------------------------

• problems with 1.1 output records under incremental redisplay
• From: Scott McKay <swm@harlequin.com>

• Prev: Bug-report: Palette-Full
• Next: Re: clos object wierdness ..
• Index: CLIM Mailing list (1-Jun-94 to 30-Jun-95)
• Thread: CLIM Mailing list Index (1-Jun-94 to 30-Jun-95)