Background groups

[Scott Rossi]

Hi Pete:

"Place" adds an instance of an existing group to a card.
Copy & paste creates a new group object.

Deleting a group physically deletes it from the stack.
Removing a group removes the instance of the group from the card, but
doesn't delete the group from the stack.


Regards,

Scott Rossi
Creative Director
Tactile Media, UX Design




On 2/8/13 11:27 AM, "Peter Haworth" <pete at lcsql.com> wrote:

>Trying to avoid any gotchas before embarking on some work involving
>background groups and there's precious little information about them.
>
>Are there characteristics of background groups other than the background
>behavior property property that must be consistent on whichever card they
>are on in order for them to behave as bg groups?  Layer/ID/ Name, for
>example?
>
>Do background groups behave differently depending on whether their shared
>behavior property is true?
>
>If I copy and paste a bg group onto a card instead of using the place
>command, does it mess up it "backgroundness"?  If not, what's
>the purpose of the place command
>
>If I delete a bg group from a card rather than use the remove command,
>does
>that in any way affect its instances on other cards?  If not, what's the
>purpose of the remove command?
>
>I notice that if I copy and paste a card with a bg group on it into a
>different stack, the bg group is still there and has its background
>property set.  If I then create a new card in this stack, the background
>group is on it.  Will it still behave like a background group linked to
>the
>background group in the original stack?
>
>Thanks for satisfying my curiosity!
>
>
>Pete
>lcSQL Software <http://www.lcsql.com>
>_______________________________________________
>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
>