On Wed, 26 Apr 2000, Alexander Larsson wrote:
> On Wed, 26 Apr 2000, James Henstridge wrote:
>
> > In fact, the renderer could handle freeing of this data by making a
> > changed signal or something. The view could then throw away the item's
> > view dependent data on changed or destroy signals.
>
> Yes, that would work. Although I think all renderer state changes
> originate from view changes, which might need all items to update
> their view-dependent state anyway. We'll see.
The other case is where you change some attribute of the canvas item (such
as the start and end points of a line item). You would need to
recalculate SVPs for that I assume.
So getting the renderer/view to store the DiaShapes sounds like a good
plan. The view could destroy all cached data on view changes (does
scrolling count as a view change?), or when a canvas item emits a changed
signal. The view would also free the DiaShapes when the canvas item is
destroyed.
I am currently (slowly) working on doing the redraw handling for
DiaCanvasView's using libart's microtile code, and Federico's UTA
manipulation code (which is currently under GPL, but I think he was
planning on relicencing it to LGPL for use in GnomeCanvas).
>
> / Alex
>
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
