oh baby i just read the blog on the profiler. I am going to have fun with this, too.
On Fri, Feb 24, 2017 at 12:27 PM, Richard Gaskin via use-livecode < email@example.com> wrote: > panagiotis merakos wrote: > > > http://quality.livecode.com/show_bug.cgi?id=19248 > > Unfortunate to see complication after complication pile up from the IDE's > insistence that stacks with the same name should not be in memory at the > same time. > > As we've discussed earlier, the engine does not appear to have such a > limitation for most operations. > > The real issue at the root of all this is the subset of actions performed > on stacks with the same name affecting the wrong stack to due an > easily-fixable limitation in how topstack is derived: > > http://quality.livecode.com/show_bug.cgi?id=18793 > > If the more complete algo employed in the FixedTopStack function provided > in comment #1 there were implemented in the engine's stack topstack > referencing, so many workflow limitations unique to LiveCode would go > away.... > > -- > Richard Gaskin > Fourth World Systems > Software Design and Development for Desktop, Mobile, and Web > ____________________________________________________________ > ambassa...@fourthworld.com http://www.FourthWorld.com > > > _______________________________________________ > use-livecode mailing list > firstname.lastname@example.org > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." _______________________________________________ use-livecode mailing list email@example.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode