From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from skinner.cs.uoregon.edu ([128.223.4.13]) by hawkwind.utcs.toronto.edu with SMTP id <2825>; Thu, 26 Nov 1992 21:27:57 -0500
Received: from sisters.cs.uoregon.edu by skinner.cs.uoregon.edu with SMTP id AA09433
  (5.65/IDA-1.4.2 for sam-fans@hawkwind.utcs.toronto.edu); Thu, 26 Nov 92 18:27:46 -0800
Received: by sisters.cs.uoregon.edu (5.61/UofO CS 27-Mar-91)
	id AA02830; Thu, 26 Nov 92 18:25:24 -0800
Date:	Thu, 26 Nov 1992 21:25:24 -0500
From:	mike@sisters.cs.uoregon.edu
Message-Id: <9211270225.AA02830@sisters.cs.uoregon.edu>
To:	jeremy@sw.oz.au
Subject: Re:  Pie menus
Cc:	sam-fans@hawkwind.utcs.toronto.edu

> [ Pie menus ]
>much more easily than moving down a linear menu.  Also, it's much faster,
>since the mouse pointer starts in the right place for all the menu items,
>rather than having the "last chosen" hack currently used.

Note that "last chosen" is not quite the hack you think it is.
It has a very desirable user-interface property.  On the average,
you end up moving the mouse up about half the time, and down
half the time.  This keeps the mouse on your desk.  By contrast,
using J. Random X utility, you continually drift off the bottom,
and have to lift the mouse up and recenter it on your desk.
Repeatedly selecting the same item in a pie menu (imagine a
"page forward" command in ghostview, for example) would still
exhibit this drifting property.  So you'd still want some sort
of "last chosen" default.

>How hard would it be to add a new menu type to sam/libXg?

Try it and see...