[comp.sys.next] Performance issues when swapping inspector views

scottsm@brahms.udel.edu (Scott M Stark) (05/25/91)

I have been looking at the /NextDeveloper/Examples/ToolInspector code to
learn about implementing an inspector panel.  I have a question
concerning the use of compositioning in the swapInspectorView() function.
This functions first composites the current toolInspector view to the 
offscreen window:
	compositeToBuffer(self,self->origin.x,self->origin.y,width,
		NX_HEIGHT(&inspectorRect),oldx,self->origin.y);
and then composites the new view into the toolInspector:
	compositeToScreen(self,newx,self->origin.y,width,
                NX_HEIGHT(&inspectorRect),self->origin.x,self->origin.y);

What are the advantages in terms of memory and performance the
compositioning gives you over simply asking the toolInspector to display
itself, that is:
	[self->toolInspector display];

When I made this substitution I did not see any significant performance
difference.  Is this just a matter of program implementation or are there
situations in which using the display message will not perform as well.

Just interested,
Scott Stark
stark@butterfly.che.udel.edu