Also of note, as I just discovered to my chagrin, is that a substack cannot have it's own stackFiles. That means any behaviors in the independent stack have to be reassociated once it becomes a sub stack.
So I think those who intend to create substacks need to take all this into account. The reason it is a big deal for me is I have a series of utility stacks that I may add to any project, the time calculator being one of them. I develop these independently from any other stack, then add them as a substack later. I have done this many times in the past and never had an issue, but I think this was before the datagrid library was moved to a script only stack. Having a single behavior I can use in multiple substacks is huge especially as I add a utility stack to more and more projects. Bob S > On Jan 17, 2020, at 11:50 , Klaus major-k via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Hi Bob, > >> Am 17.01.2020 um 20:47 schrieb Bob Sneidar via use-livecode >> <use-livecode@lists.runrev.com>: >> >> yes, but that would mean anyone who has added a datagrid to a stack wil not >> be able to make another stack it's mainStack! > > true. > >> That can't be the expected behavior. > > It is for me. :-) > But let the mothership decide if this really is. > >> Bob S _______________________________________________ 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
