🚀 go-pugleaf

In article <29942@sun.uucp>, chuq%plaid@Sun.COM (Chuq Von Rospach) writes:
> ... but I'm not sure how to build a linked list of cards
> attached to a primary card.

Well, for any linked list, all you need is to store a pointer to the next
element somewhere in the current element.  In HyperCard, the "pointer" is
the card id of the next card (a number like '12345'),
and you may as well store it in a field on each card in your list (perhaps
called "next card").  You can make the card invisible by issuing the 'hide 
field "next card"' command in the message window (this only need be done once.
Once the field is hidden, it will stay hidden until you issue a 'show field
"next card"' command).  You should probably also tick off the "lock text"
option for that field so that users can't change it's contents even if they
manage to make the field visible (you can still change the field's contents
from a script, even if lock text is switched on).  

Getting the name of the next card is quite easy if you create the cards from
a script:  something like this excerpt should do the trick.

	...
	put the id of this card into oldcard
	doMenu "New Card"
	put the id of this card into field "next card" of card id oldcard
	-- note that "this card" changes during the doMenu "New Card" command.
	...

The excerpt should be inserted in whatever script creates new cards for your
linked list.  Multiply linked lists can be handles in a similar fashion.
If your list must link cards across stacks, then you must also store the
name of the stack as well as the id number of the card.  The command
"this stack" will return the name of the current stack.

I hope this is helpful.

	Dan Freedman.
	University of Calgary Computer Science Department.