That is indeed the use case I used to justify the inclusion of the property when I contributed it. The other one was a quick way to convert an existing stack to scriptOnly without copy and paste. There was some discussion if we should add the property due to the risks to stack content when setting to true.
Cheers Monte Sent from my iPhone > On 4 Mar 2016, at 6:34 AM, Tim Bleiler <blei...@buffalo.edu> wrote: > > Since we can refer to script only stacks in our scripts exactly the same as a > regular stack, I think you could work around the problem by making your own > "pre-build" controller to loop through all your script only stacks and set > their scriptOnly property to false and then lock those stacks as you would in > the past before doing the standalone build. _______________________________________________ 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
