On 8 Dec 2014, at 6:01 am, Geoff Canyon <gcan...@gmail.com> wrote: > On Sun, Dec 7, 2014 at 12:12 PM, Peter Haworth <p...@lcsql.com> wrote: > >> My point was that a lot of people have spent time coming up with various >> ways of getting a control's owning card/stack which to my way of thinking >> means there should be a built-in way of doing it. >> > > Agreed -- here's hoping the new syntax functionality comes sooner rather > than later, so you can define something like: > > the card owner of <object> > the stack owner of <object>
I'm not sure about new syntax and if we can mess with that yet but the properties themselves wouldn't be that complicated to implement. Essentially you would just iterate through the parents of each object as you do in script to find a card or stack. I'd suggest shared group might be another good option. Both card and shared group owner could obviously be empty in certain conditions and the result of the card owner could also be variable depending on context for an object in a shared group. On the whole I'm not sure if there's a big advantage to implementing it in the engine but like I said it's not difficult. Cheers Monte -- M E R Goulding Software development services Bespoke application development for vertical markets mergExt - There's an external for that! _______________________________________________ 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
