From: jeremy@sw.oz.au (Jeremy Fitzhardinge)
To: sam-fans@hawkwind.utcs.toronto.edu (Sam Fans)
Subject: Pie menus
Date: Thu, 26 Nov 1992 20:36:05 -0500 [thread overview]
Message-ID: <9211270136.AA21018@chao.sw.oz.au> (raw)
I've just been playing around with Don Hopkins' version of twm with pie
menus, and I think I really like them.
It struck me that they would be really useful to implement sam's menus
as a pie menu, especially the middle button cut'n'paste menu. With a
small number of options, you can easily and accurately move the mouse in
the right direction to select things without having to read the label -
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.
How hard would it be to add a new menu type to sam/libXg?
J
next reply other threads:[~1992-11-27 1:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-11-27 1:36 Jeremy Fitzhardinge [this message]
1992-11-27 2:25 mike
1992-11-27 2:58 ` John Mackin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9211270136.AA21018@chao.sw.oz.au \
--to=jeremy@sw.oz.au \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).