Hmmm... I'm under the impression that in a standalone, ALL stacks besides the one in the executable are external stacks. That is, the Standalone Builder will copy any substacks to a folder as individual stacks. Even in a MacOS standalone, the package that is the app can be opened and you will find your individual stacks in Resources/_MacOS.
I'm not sure what the difference between that and what you are calling External Stacks. The Standalone (again to my mind) is simply the runtime engine glued to the main stack you compiled with it. All other stacks, including the ones referenced in the Stack Files of the main stack are simply opened like the IDE would. Bob S > On Jun 28, 2019, at 08:24 , Paul Dupuis via use-livecode > <use-livecode@lists.runrev.com> wrote: > > We have an app we're porting to LC9 (currently doing internal beta builds > under LC9.0.5rc1) that we're seeing some weirdness when external stacks are > opened by the standalone. > > This is happening under OSX. We've not seen it (so far) under Windows, but > most of our initial QA testing is done under OSX. > > When the standalone opens the external stack (which could be in an older > stack file format), when the mouse is in the external stack window, LiveCode > thinks the mouse is about 30-40 pixels ABOVE where the mouse actual is. > > It does not happen in the main stack or substacks of the standalone, just in > external stacks and, worse, it is intermittent, which means making a recipe > to report the bug to LiveCode, Ltd, difficult. > > Has anyone else seen anything like this? Even if you dismissed it as a > "fluke", I'd appreciate knowing. _______________________________________________ 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
