I'm a bit suprised that there hasn't been more response to Darryl Tang's announcement to this list of his discovery that he could use some Hypercard XCMDs to allow MacPerl to issue KeyQuencer commands.I ordered and received the full version of KeyQuencer. It changed my life. >From KeyQuencer's 'Read Me': "KeyQuencer is a utility that lets you create shortcuts, called macros, that perform a series of tasks with a single keystroke. Using KeyQuencer you can type your name, change your monitor's colors, change the sound, connect to the Internet, or do just about anything-all with a keystroke." You can also imitate mouse clicks, waiting for buttons, selection of buttons, selection of menu and submenu items, almost anything you can do with the keyboard or mouse. KeyQuencer scripts are incorporated very similarly to how Applescripts are handled in MacPerl. MacPerl can make decisions, do the work with the file system, etc., and direct Keyquencer to relieve you of the drudgery of the repetitive details. My wife and I run a small desktop music publishing business specializing in niche markets. She does the arrangements and enters the songs, using an original Mac LC's keyboard, in one long continuous staff in Professional Composer (one of the earliest professional music processors for the Mac). It's my job, using a 604 PPC (120) to open it in Mosaic (successor to Professional Composer), do the layout and make it look good enough for printing. Then I use Mosaic's PICT export capability to copy the music score (page by page) and paste it into ClarisWorks where text can be added. Then small quantities of the books are printed back side then front, one page at a time Over the years I've refined my use of Tempo II on 68xxx Macs, then Quickeys on a PPC, to automate many segments of the process. These had to be run individually for each song. A great savings of time from having to do everything manually everytime. Our latest publishing project has one fiddle tune for each day of the year for the year 2000, or 366 tunes (leap year). I was working on converting January's tunes and realizing how long this project was going to take me when I read Darryl's post. Using MacPerl to drive KeyQuencer has saved me countless HOURS. I can now put a series of KeyQuencer scripts in my MacPerl programs to process a whole folder of files at a time. I still have to do segments of the project at a time but now I can do them in batches. And best of all, KeyQuencer's code is relatively very easy to learn and less geeky. David Seay http://www.mastercall.com/g-s ===== Want to unsubscribe from this list? ===== Send mail with body "unsubscribe" to macperl-request@macperl.org