Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!udel!new
From: new@udel.edu (Darren New)
Newsgroups: comp.sys.amiga
Subject: Re: PowerPacker 2.2a problems
Message-ID: <898@nigel.udel.EDU>
Date: 5 Oct 89 19:11:36 GMT
References: <1989Sep20.221509.4401@edson.ee.UAlberta.ca> <1837@convex.UUCP> <1858@sactoh0.UUCP>
Sender: usenet@udel.EDU
Reply-To: new@udel.edu (Darren New)
Distribution: na
Organization: University of Delaware
Lines: 15

In article <1858@sactoh0.UUCP> hrlaser@sactoh0.UUCP (Harv R. Laser) writes:
>What PP needs is a 'config' file to save parameter changes
>so one can customize the menu choices to his liking and have
>the program load with those settings each time it's run. 

Actually, you could write a program that you give it the name of the
screen and window and a menu option.  That program would wait for that
screen, then that window, then the menu to appear, and then would
hook into the input.device and pass on a MenuPick message (or whatever
it's called) to the window.  Then we would have a generic configuration
program for anything with menus.  Then we put it in ARexx scripts and
viola (:-), we're running menu-only program that don't have ARexx
ports from ARexx!  Now, could this be done with keys, too?  You
betcha.   Hmmm....  I wish I had as much time as ambitions...
		   -- Darren