🚀 go-pugleaf

In article <9208250426.AA26138@sparc0.brc.uconn.edu>, sriram@brc.uconn.edu (Chittathoor M. Sriram) writes:
|> 	I have an application in 3.0 in which I append a large number of 
|> 	components in Page Glyph which is inside a Patch object. 
|> 
|> 	Inside my program I also dynamically append components to the page and 
|> 	then do the following:
|> 
|> 	patch->reallocate();
|> 	patch->redraw().
|> 
|> 	This works fine but it was very slow as it did a redraw of every 
|> 	component.  
|> 
|> 	I tried out the same application by just calling  patch->reallocate() 
|> 	after appending dynamically the components to the page.
|> 	The result was a gain in speed. 
|> 
|> 	What I am wondering is if the call to patch->redraw() is necesary as 
|> 	even without that it seems to be working.  
|> 
|> 	I dont understand why the call to patch->redraw() is necessary
|> 	if just calling patch->reallocate() seems to do the job.
|> 
|> 	Will there be any side effects.

Patch::redraw will definitely redraw the entire page.  Patch::reallocate
is sufficient here because the Page will damage the changed areas
during its allocation.  If you were using some other aggregate, such
as a box, a reallocate would not incur the appropriate damage.