>One time there was a debate on the SuperCard mailing list about which was
>better: runtime editing, or the more modal technique employed by
>SuperEdit. At the time I didn't care much one way or the other, but one
>comment made by a SuperEdit proponent is echoing in my mind right now: he
>said something like, "I prefer to perform surgery on my projects without
>the patient squirming around on the table while I do it."
>
>I'm finding that I miss SuperEdits "no scripts" environment, and even the
>"scripts only run when you're running the project" aspect of SuperCard's
>standard editor. I use on openCard messages to trigger things to happen
>in my program (an educational product), and they seem to go off even if I
>don't have the browse tool selected.
> As a defense, I've stuck in a front
>script that traps openCard, closeCard, openBackground, and
>closeBackground messages. Is this the best way to stop MetaCard from
>automatically moving me on to the next card, etc., or is there something
>I'm missing?
>
>Thanks
>
>gc
The easiest way is to identify which cards do what when they open:
on openCard
if the short name of this cd is "b" then beep
end openCard
...otherwise any openCard can trigger "beep".
Regards, Andu
