Naming Conventions

[Phil Davis]

If you have handlers that reference same-named controls residing in different stacks, you can either:

- use fully qualified control names (which can get wordy)
    set the hilite of btn "yes" of current card of stack "firstStack" \
        to the hilite of btn "yes" of current card of stack "secondStack"

- use "the defaultStack" to shorten the references (which adds lines)
    set the defaultStack to "firstStack"
    get the hilite of btn "yes"
    set the defaultStack to "secondStack"
    set the hilite of btn "yes" to it

- do something else I haven't thought of


FWIW.

Phil

----- Original Message ----- 
From: "Gregory Lypny" <gregory.lypny at videotron.ca>
To: <metacard at lists.runrev.com>
Sent: Monday, July 08, 2002 7:50 AM
Subject: Naming Conventions


> Hi Everyone,
> 
> I have a  multi-stack project with a number of information stacks 
> that are very similar in structure, for example, a title field, text 
> body field, and card navigation buttons.  Is it a problem if these 
> controls have the same names in the different stacks?
> 
> Regards,
> 
> Greg
> 
> _______________________________________________
> metacard mailing list
> metacard at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/metacard