strange nested groups behaviour

[John Tregea]

Hi JB,

This is not the perfect approach but should solve the strange behaviour. 
If this fragment was put in place of the line that has "the owner of the owner of me"

repeat with x = 1 to 12
 if the id of group ("search" & x) is in the long name of me then exit repeat
end repeat
put ("search" & x) into tMyGrandparent
-- now you have the name of the ultimate owner of the field.

In my nested group heirarchy I set a custom attribute for the sub groups and objects in the group called "parent_group". That way I can get the parent_group of the owner of me...

HTH

John

>-----Original Message-----
>From: Stephen Barncard [mailto:stephenREVOLUTION at barncard.com]
>Sent: Wednesday, September 12, 2007 01:42 AM
>To: 'How to use Revolution'
>Subject: Re: strange nested groups behaviour
>
>I think it's always a good idea to NOT name anything with system keywords.
>And you're in for real problems naming custom properties with the 
>same name as system properties, quotes or no quotes. Rev doesn't like 
>that. Custom Properties, too sometimes have problems when they start 
>with a number.
>
>>On 10 Sep 2007, at 23:03, Mark Wieder wrote:
>>
>>>jbv-
>>>
>>>In addition to the above weirdnesses with the owner of a group, I think it's
>>>also bad form to use a keyword as the name of an object. You'll probably
>>>stay out of trouble more if you name it something like "grpDate". YMMV.
>>
>>Can you elaborate on why that would be bad form? I never had 
>>problems with naming things the same as a keyword, as long as I 
>>quoted the name, which I always do.
>>
>>I did however have problems with using only numbers as names, or 
>>starting a stack's name with "rev".
>>
>
>-- 
>
>
>stephen barncard
>s a n f r a n c i s c o
>- - - - - - - - - - - -
>
>
>
>_______________________________________________
>use-revolution mailing list
>use-revolution at lists.runrev.com
>Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>http://lists.runrev.com/mailman/listinfo/use-revolution
>