Path: utzoo!utgpu!water!watmath!clyde!att!pacbell!ames!pasteur!ucbvax!decwrl!purdue!gatech!udel!rochester!pt.cs.cmu.edu!cadre!pitt!cisunx!ejkst
From: ejkst@cisunx.UUCP (Eric J. Kennedy)
Newsgroups: comp.sys.amiga
Subject: Re: Poll of net tastes
Message-ID: <9875@cisunx.UUCP>
Date: 20 May 88 08:17:09 GMT
References: <6598@cit-vax.Caltech.Edu> <531@osupyr.mast.ohio-state.edu> <2856@polya.STANFORD.EDU>
Reply-To: ejkst@unix.cis.pittsburgh.edu (Eric J. Kennedy)
Organization: Univ. of Pittsburgh, Comp & Info Sys
Lines: 38

In article <2856@polya.STANFORD.EDU> rokicki@polya.Stanford.EDU (Tomas G. Rokicki) writes:
>Seriously, though, I would like a hot-key program to be able to do this,
>somehow, based on the program name in the CLI, maybe, or maybe the title
>bar name, or something.  I consider the SYSTEM key to be one of the
>greatest user interface features since the stoplight.

I would, too, but then I run into the problem of 
_Too many %##&&!! Hotkeys_!!  I mean, really, f1 is about 93 different
things to me, depending on what program I'm in.  Add a hotkey
application launching program and you just add to the general mess.

So, it's not exactly using the 'system' key, but I'm in the process of
debugging a program that puts a tiny window in the workbench screen,
with a large customizable menu that can start your text editor, or
whatever.  There's room for over 90 menu items, if you want to get
excessive.  The idea is like the MAC Desk Accessory menu--it's always
there, ready for you to lauch an editor, graphics program, game, change
fonts, diskchange df2:, etc.  (And *NO* this is not another "make amy
more like a MAC.  I thought of this program before I ever used a MAC.
So there.)

Only... I keep guruing with a 'memory freed twice' error when I'm
messing with the linked list structures.  I'm following Rob Peck's
example in the April TransAmi as close as I can, as this is my first try
at using the exec list stuff.  The problem is extremely unpredictable.
I'll run it successfully 5 times in a row, and then an H-bomb goes off
in my face leaving no survivors, not even VD0:.  Any suggestions?

Anyway, assuming I can get the memory problems squared away, if there is
interest, I can mail it, or submit it to binaries.


>-tom

-- 
------------
Eric Kennedy
ejkst@cisunx.UUCP