Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!shawnee.cis.ohio-state.edu!tj From: tj@shawnee.cis.ohio-state.edu (Todd R. Johnson) Newsgroups: comp.sys.amiga Subject: Re: PowerPacker 2.2a problems Message-ID: <65039@tut.cis.ohio-state.edu> Date: 5 Oct 89 20:10:12 GMT References: <1989Sep20.221509.4401@edson.ee.UAlberta.ca> <1837@convex.UUCP> <1858@sactoh0.UUCP> <898@nigel.udel.EDU> Sender: news@tut.cis.ohio-state.edu Reply-To: Todd R. Johnson Distribution: na Organization: The Ohio State University Dept of Computer & Information Lines: 25 In article <898@nigel.udel.EDU> new@udel.edu (Darren New) writes: < 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! < -- Darren Hmmm.... Sounds like you need ScripIt. I believe that it will do everything that you want and more. Scripit even has an ARexx port and a program that will take a scripit script and turn it into a directly executable program. To make scripts you can write them by hadn or use a recorder to generate an initial script. The entire package is very nice. I got the latest version off a local BBS. ---Todd -=- ---Todd tj@cis.ohio-state.edu