> In my experience, MetaCard is a little less reliable > than HyperCard when it comes to traversing the message > hierarchy. In my case : when a button calls a handler in the > stack, AND THEN calls a handler which is in the btn AND in > the stack, MetaTalk will oddly select the handler in the > stack instead of the one in the button.
I just tried this in MC 2.5.1 and it doesn't perform as you describe; it calls the handler in the button and not in the stack. I did this: <button script> on mouseUp DoThis DoThat end mouseUp on DoThat put "that" after msg end DoThat <stack script> on DoThis put "this" after msg end DoThis on DoThat put "stackthat" after msg end DoThat When I ran it, I got "thisthat" in the message box, not "thisstackthat". At first I thought it might have to do with HyperCard importation, but when I set the hcAddressing and dynamicPaths of the stack to true, I got the same result. Perhaps you recall this in an earlier version of MC? Ken Ray Sons of Thunder Software Email: [EMAIL PROTECTED] Web Site: http://www.sonsothunder.com/ _______________________________________________ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard
