On Wed, Aug 9, 2017 at 11:08 AM, Paul Dupuis via use-livecode < use-livecode@lists.runrev.com> wrote:
> Has any one run into the following situation in LiveCode standalones? > > In a multiple window application, the user has either a standard window > or a modal dialog open (the topWindow which is also the defaultStack). > They navigate to a 3rd party application and by some means back to the > LC standalone and click a control in the topWindow (again either a > standard window or dialog) and that window is NO LONGER the defaultStack > so an execution error occurs on the first control referenced that is not > fully qualified. > > Obviously, I can fix this by fully qualifying all my object references > (i.e. instead of using fld "x", using fld "X" of stack "Y") but I am > curious is anyone else has seen anything like this? > I think this bug report has a recipe for the issue you are seeing: http://quality.livecode.com/show_bug.cgi?id=18030 This has been around for a long time. I don’t know of a workaround other than fully qualifying all object references. -- Trevor DeVore ScreenSteps www.screensteps.com _______________________________________________ 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
