The Owner of a background group

[dunbarx at aol.com]

Pete.


I would worry that cards can be shuffled. And using the "place" command can target any card.



I would think that a library handler that automatically sets the "progenitor" property on group creation would be best. You can always ignore it.



Craig




-----Original Message-----
From: Peter Haworth <pete at lcsql.com>
To: How to use LiveCode <use-livecode at lists.runrev.com>
Sent: Mon, Aug 20, 2012 9:08 pm
Subject: Re: The Owner of a background group


I agree with that, that's why I thought the behavior I was seeing was so
weird.  I started using a fresh copy of the stack and all now works as
expected so there must have been some corruption in the version of the
stack I was using.

There might be an existing way to find out the "progenitor" - the cardNames
of a group gives a list of all the card names that group appears on and,
without exhaustive testing, it appears that the first line of that list
might be the progenitor.

Pete
lcSQL Software <http://www.lcsql.com>



On Mon, Aug 20, 2012 at 5:28 PM, <dunbarx at aol.com> wrote:

> Bob.
>
>
> It seems more natural to me that the owner is the current card. It makes
> the message hierarchy consistent.
>
>
> The "progenitor" could be a property as you suggest, but since this is not
> native, just set a custom property of the group to the id of the card that
> gave it birth. You then get everything you could ask for.
>
>
>
> Craig
>
_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode