Phil Davis
Sun, 24 Sep 2000 14:01:52 -0700
David Bovill wrote: > > As part of my campaign to make distributable components out of Metacard > groups... I find myself dissatisfied with the way that Metacard looks for an > object by name. > > I am at the moment writing for every single object reference that I script > something like: > > put "hello" into fld "Text" of the owner of me > > The reason for this is just in case there is another field named text in the > environment. Now this is beginning to annoy me as it is long winded. I would > prefer "fld Text" to refer first to a field named text within the current > group, and then anything in groups within any groups in that group, and not > to something outside of the current group unless I explicitly say so. So this new thing would allow shorter references to objects within a group when more than one group exists, similar to the way "the defaultStack" allows shorter references to objects within a stack when you have multiple stacks open. So it kind of sharpens the focus of the reference, or more specifically defines their context. Correct? > > Now as this would clearly cause too many compatibility problems, how about a > little change so that I can set an object property (stack or group), so that > when "groupReferences is true" all references to controls are within the > current group (ie the owner)? This should apply to numbers as well as names. > > Archives: http://www.mail-archive.com/metacard%40lists.best.com/ > Info: http://www.xworlds.com/metacard/mailinglist.htm > Please send bug reports to <[EMAIL PROTECTED]>, not this list. -- Phil Davis ----------------------------------- [EMAIL PROTECTED] days: (503) 417-7930 eves: (503) 557-5656 ----------------------------------- Facilitator Essentials of eBusiness Computing Information Technology Institute http://www.iti.com Archives: http://www.mail-archive.com/metacard%40lists.best.com/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to <[EMAIL PROTECTED]>, not this list.