Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!pasteur!ucbvax!gergle.UUCP!greg
From: greg@gergle.UUCP
Newsgroups: comp.windows.news
Subject: Re:  beginner NeWS questions
Message-ID: <8805020520.AA06058@parallax.parallax.com>
Date: 2 May 88 06:39:06 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 41


	
	  - Is there a way for psterm not to scale the font, and just change
	    the window size? The documentation says no.
no.
	
	  - Is there a way for psterm to understand multi-click text selections,
	    e.g. one click is for characters, two clicks is for words, etc. ala
	    shelltool? The documentation says no. If not, why not? I think this
	    is a really good feature. 
no. Read the chapter 5 on extended input.
	
	  - Can someone explain why moving a window over the "Group" root background
	    is significantly slower than over the "Plain" background when moving the
	    entire window contents?

In Short, Group Root is a stupid client.

It does not do intelligent damage repair.  The time delay you are seeing is
the processing time for drawing the logo in PostScript.  If you move a window
in the center of the screen, damage will occur to the root canvas. (Unless 
you have a retained root canvas)
The PostScript procedure which draws the group root picture draws the whole 
thing, regardless of the area damaged.  The time to process the path and 
prepare for filling is significant even though the C drawing functions 
will trivial reject the area to be filled before actually painting bits.

You could speed things up considerably by checking to see if the bounding
box of the current clip intersects with the bounding box of the logo at damage
repair time.
	
	  - How do I list out the procedure names in the global CaretShapeDict dictionary?

psh
CaretShapeDict { pop == } forall 

will get you all the keys in the dict. You could check the "type" of
the values and filter for executable arrays if you just want procedures.
	

	-greg.