panagiotis merakos wrote:
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:
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....
Fourth World Systems
Software Design and Development for Desktop, Mobile, and Web
use-livecode mailing list
Please visit this url to subscribe, unsubscribe and manage your subscription