Re: Moving output records for fast translation

• To: pkarp@Sunset.AI.SRI.COM
• Subject: Re: Moving output records for fast translation
• From: "John G. Aspinall" <JGA@stony-brook.scrc.symbolics.com>
• Date: Fri, 1 May 1992 17:04-0400
• Cc: clim@BBN.COM
• In-Reply-To: <CMM.0.90.2.704750175.pkarp@Rockaway.AI.SRI.COM>

    Date: Fri, 1 May 1992 15:32 EDT
    From: "John G. Aspinall" <JGA@stony-brook.scrc.symbolics.com>

	Date: Fri, 1 May 1992 13:39 EDT
	From: Peter Karp <pkarp@ai.sri.com>

	[...] My theory is that it will be faster to get CLIM to redraw the output
	records associated with those picture elements, with a translation
	applied, than it will be to completely redraw those picture elements
	at the application level (particularly if much computation is required
	at the application level).

    Certainly.  This is what (e.g.) dragging-output does.

    Date: Fri, 1 May 1992 15:56 EDT
    From: Peter Karp <pkarp@ai.sri.com>

    The type of translation I had in mind is not interactive --
    the application knows exactly where the output record should
    be moved -- therefore dragging-output is not useful for this task.

You misunderstand.  I never suggested that you use dragging-output.
I was saying that dragging-output has the same requirements as you do.
In both cases, the requirement is to "redraw under translation as fast
as possible".

I should have said:

Certainly.  This is what (e.g.) dragging-output does to achieve the same goal.

• Re: Moving output records for fast translation
• From: Peter Karp <pkarp>

• Prev: Re: Moving output records for fast translation
• Next: Moving output records for fast translation
• Index: CLIM Mailing list (1-Jan-92 to 31-Aug-92)
• Thread: CLIM Mailing list Index (1-Jan-92 to 31-Aug-92)