Tom, If you plan on saving changes with your project, you'll find you can't do it in a mainstack. You have to use substacks as only they can be 'saved.'
This is a limitation of Linux,PC and MacOSX executables. Many people use a mainstack as a 'Splash Screen' which then loads all the necessary substacks. In this way, you could even have your substacks located on a server and download them from the Main Splash Screen if you like. That way your users would always have the latest version. You can of course also write data files directly to a users hard drive and load them into a main or substack if you like. This will get you around the limitation of not being able to save a mainstack. best, Chipp > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of tom farrell > Sent: Monday, June 02, 2003 7:11 PM > To: [EMAIL PROTECTED] > Subject: newbie: when to use substacks? > > > Hi... > > Any pointer/hints/suggestions/reminiscences about when you decide to > use a main+substack design rather than just one monolithic main stack? > > thanks in advance for any time you might have for a reply. > > tom > _______________________________________________ > use-revolution mailing list > [EMAIL PROTECTED] > http://lists.runrev.com/mailman/listinfo/use-revolution > _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
