>Gregory Lypny wrote:
>
>> How do I divide my MC stacks into navigable sections? For example,
>> if I have a stack with two sections ("backgrounds" in the HC paradigm), I
>> would like to have a background field in each which displays the card
>> number and total number of cards in those sections as "Card 3 of 36" and
>> "Card 7 of 82".
>
>In my project, which is a tutorial, I achieved this goal by judicious
>naming of my cards. For example, the cards in my Introduction section
>are named "Introduction 1" and "Introduction 2"; the cards in my
>Concepts section are named "Concepts 1" and "Concepts 2" and so on. That
>way I can script a command like
>
> go cd "Concepts" && n --where n represents the card number within the
>section.
>
>This presents some annoyances if I need to add a card between two cards
>in a section, because all the subsequent cards in the section need to be
>renamed, but since I rarely have more than 10 cards in a section, and
>since the only hard-coded "go" commands I use are for card 1 of a
>section, it generally works really well for me, and I didn't have to
>script anything special to move users from the end of one section to the
>beginning of the next; they just click the Next button, which uses "go
>next cd". I also have various routines that do things like counting up
>the number of cards in each section & displaying the user's place in the
>section (e.g., "Screen 2 of 5").
>
>Another way to approach this would be to put each of your sections in a
>separate stack or substack, so instead of
>
> go cd 1 of bg "B" --HyperCard way
>
>you would use
>
> go cd 1 of stack "section B" in window of this stack --MetaCard way
>
>I'd be interested to know how other people deal with this.
>
>BTW, I think you will soon find the ability to put several backgrounds
>(or groups, in MetaCard-speak) on one card to be really useful. It lets
>you reuse a set of objects as needed without having to copy them from
>one card to another or hide/show them from the background.
>
>--
>Marni Centor ([EMAIL PROTECTED])
I have, so far, 80 different stacks in the project I'm working with right now. The
main reason for that is to keep stack size down. Some of them have several backgrounds
which they share.
Some backgrounds have graphics which are shared and some backgrounds only have a bunch
of scripts being shared and no visible items. I even have a background "just being
there", to be checked for and sertain things will happen if it's there or not.
As soon as you get used to using the backgrounds in MC you'll see lots of
possibilities.
Regards,
Eva
xxxxx
Eva Isotalo
Haparanda, Sweden
xxxxx
