Naming Conventions

[erik hansen]

> - do something else I haven't thought of

* use labels. use the same label (say "Enter")
for btns in different stacks but use names for
the controls that differ in each stack. 

use ids.

--- Phil Davis <phildavis at attbi.com> wrote:
> 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

> > 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?


=====
erik at erikhansen.org    http://www.erikhansen.org

__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com