From: Roy C. Crisman
Ian, I haven't used the behaviors you are talking about, but maybe try this:
Have the Fields that are filled in by the user as single, long sprites. As you
come to page one, you fill in page one's sprites. As you go to page two, those
sprites are still there, but you've moved them off the screen (still a single
sprite span), and the page two fields start. Page three has page one and page
two sprites moved off screen and new page three field sprites. Then when the
submit behavior fires, it gets the field information from ALL the sprites, cause
they're all still on the page, just off screen.
Or you could write some custom lingo to store all the field information as you
go, but you didn't sound too confident about programming custom Lingo, which is
why I suggest this work-around.
roymeo
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
