no, they should go to the program, since it's the one that set up the listener, et al. the applescript does the equivalent of opening the terminal and running a program in it, with keyboard and mouse events going directly to the program.
besides, i haven't used the script in years, preferring to start from the terminal instead. On Sun, Apr 6, 2008 at 3:22 PM, Skip Tavakkolian <[EMAIL PROTECTED]> wrote: > wouldn't the appleevents go to the drawterm applescript you > and Paul posted a while back? this one: > > do shell script "cd ~ && drawterm -a somebox -c somebox" > > so maybe the applescript needs to field or forward those? > > > > > i've lost my notes on this, but basically you need to figure out why > > the drawterm Carbon event handlers are not being called. it could be a > > configuration option that we're not setting or something more > > sinister. i don't know enough osx to be able to say. > > > > another manifestation of the same bug which may be easier to debug, is > > when you do apple-Q while in full-screen mode. the apple-q never > > arrives at the keyboard handler for drawterm and consequently the code > > never does a proper "exit". what's the difference between fullscreen > > and windowed mode according to OSX is beyond me. > > > > i'm sorry, i know this doesn't help much. > > >
