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 -----Original Message----- From: Bob Sneidar <b...@twft.com> To: How to use LiveCode <use-livecode@lists.runrev.com> Sent: Mon, Aug 20, 2012 6:36 pm Subject: Re: The Owner of a background group Never mind works the same either way. Frankly, I would like the owner to return the card it was originally on. It seems confusing to me that the owner would change when the active card changes. Doesn't seem intuitive. I suppose however, this might allow for the deletion of the "owner" card without deleting the group that is placed on multiple cards. I thought it might be related to behaviors but nada. I cannot make it work where the owner is the first card the group was placed on/created on. Bob On Aug 20, 2012, at 2:59 PM, dunb...@aol.com wrote: > Bob. > > > I am intrigued. > > > > Craig > > > -----Original Message----- > From: Bob Sneidar <b...@twft.com> > To: How to use LiveCode <use-livecode@lists.runrev.com> > Sent: Mon, Aug 20, 2012 5:53 pm > Subject: Re: The Owner of a background group > > > Behave as background on? > > Bob > > > On Aug 20, 2012, at 1:56 PM, Peter Haworth wrote: > >> Hi Craig, >> Interesting, I wonder what's different in my situation. It's not my stack >> that exhibits this behavior so hard to dissect it. Maybe it's some other >> setting of the group that is causing the behavior. >> >> I used the message box to check this out: >> >> put the long ID of the owner of GroupA of Card2 of stack xyz >> >> That returned a long ID which included the ID of Card1, not Card2. Same >> thing if I asked for the owner of a control within GroupA >> >> Very weird. >> >> OSX 1.7, LC 5.5.1 >> >> Pete >> lcSQL Software <http://www.lcsql.com> >> >> >> >> On Mon, Aug 20, 2012 at 1:38 PM, <dunb...@aol.com> wrote: >> >>> Peter. >>> >>> >>> I don't see this. >>> >>> >>> >>> I made a card and a background group, I made a background field that, on >>> opencard, would show the owner of the group. I made a few new cards. >>> Navigating, the owner of the group is the current card, not the first card >>> where all the authoring took place. Using the "place" command works the >>> same as "command-N" in placing the group onto downstream cards. >>> >>> >>> >>> Mac OS10.5, LC 5.5 >>> >>> >>> Craig Newman >>> >>> >>> >>> >>> -----Original Message----- >>> From: Peter Haworth <p...@lcsql.com> >>> To: How to use LiveCode <use-livecode@lists.runrev.com> >>> Sent: Mon, Aug 20, 2012 4:19 pm >>> Subject: The Owner of a background group >>> >>> >>> It appears that requesting the owner of a background group does not always >>> return the card on which the group exists. I think it returns the card on >>> which the group was initially placed. >>> >>> For example, if groupA is a background group initially placed on Card1, >>> then placed on card2 and I ask for the owner of groupA on Card2, I get >>> Card1. >>> >>> Given that I'm not misunderstanding this, how can I discover which card a >>> specific instance of a background group is on? >>> >>> Pete >>> lcSQL Software <http://www.lcsql.com> >>> _______________________________________________ >>> 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 >>> >>> >>> _______________________________________________ >>> 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 >>> >> _______________________________________________ >> 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 > > > _______________________________________________ > 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 > > > _______________________________________________ > 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 _______________________________________________ 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 _______________________________________________ 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
