>So the solution has to be to avoid modal dialogs. You could do that by >creating your own dialog stack and storing it as a substack in your main >stack. You'd fill the text field with the appropriate response and set >the button labels to whatever you want. Then display it as modeless: > > modeless "myDialog"
This would definitely be an option for the current project... Though I'm wondering how other projects will fare. Remembering a piece of code in Pork Barrel, where I have several soundchannels playing at the same time, each in a repeat loop, while a whole series of visuals and images do things on the screen, while at the same time other handlers are running in the background... (I think this is the part where you hit Saddam Hussein with a bomb and blow him out of the desert, to the sounds of planes and bombs and screams to appropriate visual effects to show you were successful :-) I'll tell you, it took me awhile to work out the soundChannel scripts, as even my wondrous Hypertalk 2.2 didn't give quite enough detail, but once I figured it out, it sure opened up a whole world of sound! No doubt Hypercard had a lot of hidden talents that weren't well documented. Too bad Apple abandoned it. I held out as long as I could before switching. I picked a really good time to switch, as I'm getting into projects I want to release cross platform, and one very enthusiastic project which could be done in Hypercard, but it sure will fare much better in Metacard. In fact, I'm starting to see ways of doing things in Metacard that will make me a very happy programmer when I get back to work on this project :-) (Actually started it in Hypercard a long while back, and got distracted away from it into other projects.) Can't wait to get back on it now! -- --Shareware Games for the Mac-- http://www.gypsyware.com _______________________________________________ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard