I think I figured it out. Thanks for the ideas about troubleshooting but none of those rabbit holes were particularly informative.
Eventually while doing something else I went back through the dictionary entries for the various commands that make use of external stacks. It finally dawned on me that I had mindlessly listed this actual stack in the same "start using" list as all of my script only library stacks. Then I was also using "go to stack" when the user actually opened it. So that makes sense, right? The reason it was getting every message like a library stack is that I told Livecode to use it as a library stack. I think I understand the different options a little better now. All I need is "go to stack" with the file path at the moment I need the mainstack; I don't have to include it previously or anything. On Wed, Apr 5, 2017 at 9:29 AM, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > the executionContexts > Bob S > > On Apr 4, 2017, at 19:22 , Matt Maier via use-livecode < > use-livecode@lists.runrev.com<mailto:use-livecode@lists.runrev.com>> > wrote: > > I'm not aware of a way to "trace" where a message has been and the keywords > I can think of aren't turning up anything promising in the dictionary or > google. > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
