iOS: second stack in memory disrupts message flow

J. Landman Gay jacque at
Wed May 8 13:30:45 EDT 2013

On 5/8/13 8:52 AM, Ben Rubinstein wrote:

> For now, I've rewritten things so that the prefs stack is opened,
> everything is moved to globals, then the stack is immediately closed and
> removed from memory; and on shutdown, the prefs stack is opened again,
> globals are moved to properties, the stack is saved and then closed.
> This restores normal message routing - is it the best solution?

I usually just reset the defaultstack. The topstack isn't always the 
defaultstack, so setting your main stack to topstack won't always work. 
Wrap the offending handler in a couple of lines of script that save the 
current defaultstack, do some work, and then reset the defaultstack.

Jacqueline Landman Gay         |     jacque at
HyperActive Software           |

More information about the use-livecode mailing list