well, 1st quittin gthe app, and then doing this, the script opens for editing. *but*, quitting the app and 2-clicking the script *also* opens it for editing. So, it seems as if this is an intermittent problem. I'm fairly sure that if I reboot and try these things i'll see the 2-click problem, and maybe the other too. let's see ... [rebooting] ...
after the 1st reboot, drag&drop launched macperl and opened the file for editing (as it should); quitting and 2-clicking did the same. after the 2nd reboot, 2-clicking the script launched macperl and opened the file for editing; quitting and d&d did the same. repeatedly, 2-clicking and quitting, *cannot* reproduce the problem now. so, this is a very intermittent problem ... can anyone here see the way to make it always happen? Bill Becker wrote: > > What if you drag the script on top of the MacPerl program icon? > > At 11:55 -0800 12/09/2002, Richard Cook wrote: > >Dave Linton wrote: > >> > >> On Wed, 4 Dec 2002 15:24:35 -0500 Chris Nandor wrote: > >> >So what else has changed since 5.6.1r1? > >> >* Fixes for running scripts on startup (Alex Harper, et al) > >> > >> Hmmm ... > >> > >> I still can't launch scripts by double clicking a droplet or dropping a > >> folder or document on a droplet unless MacPerl is already running. > >> (macperl-Bugs-489132) I thought the fix mentioned above covered this ... > >> > >I'm also still seeing this problem: double-clicking a script in the > >Finder launches MacPerl, but doesn't (always? ever?) open the script > >for editing. > > > >-Richard
