I'm working on an iPad app that is essentially a photo book. I've created a big scrolling group of images that are 1024 x 768, and a mobile controller to manage the scrolling. A couple of chapters are longer than 30+ pages, and were not scrolling as expected. It took me a while to realize I was encountering a limit to the width of the content of a scrolling group. Reorganizing the chapters to be less than 30+ pages each is not an option at this point.
Has anyone come up with a strategy for dealing with very large scrolling groups? I'm working on splitting the content into 2 groups, and a way to jump from one to the other. It would be nice if it was relatively seamless, but that's not essential. I expect I'll have to insert a sort of "read more..." button at the "end" of group 1, hide group 1, show group 2, reset the scroll of the mobile control to zero... and continue on scrolling. Then reverse the whole process to go from group 2 to group 1. Back in the Supercard days, I once worked on a Myst-like game. I used just 2 cards for most navigation, switching back and forth between them and changing the graphics on the hidden, non-active card dynamically in response to the next "step". All the navigation choices/options were held in a flat-file database, so edits and maintenance was really convenient. I can vaguely imagine something like that with this scrolling issue... but haven't figured out how it would all happen smoothly and seamlessly.... Any insights? Thanks, - Charles -- Charles E. Buchwald http://buchwald.ca Vancouver / Mexico City / NYC Member of the 02 Global Network for Sustainable Design • Connect on LinkedIn • Follow me on Twitter _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
