The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Andrew Hume <andrew@humeweb.com>
To: Noel Hunt <noel.hunt@gmail.com>
Cc: The Unix Heritage Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Jerq menuhit/mhit
Date: Thu, 29 Jun 2023 15:22:47 -0700	[thread overview]
Message-ID: <88993DC3-99D0-4977-A410-2BCAED781245@humeweb.com> (raw)
In-Reply-To: <CAGfO01xxNVPX0=V6WS05UHjiCx3VPf-pRuPba2c1mRgRaMpAww@mail.gmail.com>

i remember mhit well.

generally, most folks thought the user interface had gone wrong
if you needed to handle such large lists in a menu. so there was
a mild cultural prejudice against such things.

however, i needed it for a couple of projects, including circuit layout
software. you can imagine selecting chips from such a menu
and so on.

> On Jun 29, 2023, at 3:15 PM, Noel Hunt <noel.hunt@gmail.com> wrote:
> ...

> The earliest version in the Eight Edition jerq code, also has
> one function in the NMenu structure which is called when the
> mouse pointer invokes a hierarchical menu. By Ninth Edition
> this has been expanded, with 3 functions, one as above, one
> invoked when an item is selected ('hit') and one when a
> hierarchical menu is exited.
> 
> In the jerq code directories, under 'lib/jj', is a small 'ms'
> document, 'A Library of Goo for the 5620', which lists
> routines available in the library, and their authors. Andrew
> Hume is listed as the author of 'mhit'.
> 
> Are there examples of code using these three menu functions
> ('dfn', 'hfn', 'bfn')?


  reply	other threads:[~2023-06-29 22:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 22:15 [TUHS] " Noel Hunt
2023-06-29 22:22 ` Andrew Hume [this message]
2023-06-30 15:28   ` [TUHS] " Seth Morabito
2023-06-30 22:14     ` Rob Pike
2023-07-02  7:10       ` arnold
2023-07-02 14:13         ` Dave Brown
2023-07-02 14:27           ` arnold
2023-07-02 15:14 Norman Wilson

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=88993DC3-99D0-4977-A410-2BCAED781245@humeweb.com \
    --to=andrew@humeweb.com \
    --cc=noel.hunt@gmail.com \
    --cc=tuhs@tuhs.org \
    /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).