On Mon, Jan 22, 2018 at 12:20 AM Geoff Canyon via use-livecode < use-livecode@lists.runrev.com> wrote:
> It occurs to me that this isn't as much of a problem as I thought -- any > button being converted to a stack is highly unlikely to have an openstack > handler already in it, and therefore it would be safe to add one and > include setting the behavior of the script-only stack to the appropriate > stack up the chain. If there were already an openstack handler in the > chain, then the conversion process could stop at that point, or perhaps log > the error to the user. Unless I'm missing something? Geoff, Keep in mind that script only stacks that are loaded into memory by the engine because they are referenced in the stackfiles of another stack won’t be sent any messages. http://quality.livecode.com/show_bug.cgi?id=18223 You have to complete the behavior chain in the openStack handler of the stack that is being opened. I think in your case you would process the openStack message in the stack you are setting the stackFiles on. Trevor DeVore ScreenSteps > _______________________________________________ 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
