On Sun, 2003-07-20 at 02:12, Barry Levine wrote: > This may sound strange but I've only been developing single-stack > standalones. I've used text files to store various params. > > I now have to create a three-stack solution; at least, I think three > stacks is the proper design. I'd appreciate any advice regarding the > project as I describe it below: > > Stack #1: Splash screen containing the standalone engine. No changes to > this stack once it's compiled. > > Stack #2: Sign-in stack containing a few buttons and a field. The > buttons contain the code that adds/deletes user names to/from the > field. Other code in the buttons will also create/delete folders named > for each user. > > Stack #3: The "business" part of the program containing a number of > cards. Each card contains a few QT Player objects and the code > contained in the stack (and/or buttons in the stack) will permit the > user to link to photos or movies on the local hard drive. > > This all seems quite straightforward to me except for one thing (which, > as I indicated above, I've never done): What is the Transcript code I > would use to call Stack #2 from Stack #1 and close Stack #1's window so > it's not seen for the rest of the program? > > Would this work?: > > open stack "stack #2" > close stack "stack #1" > > ...or would this simply exit the program? > > Should I just hide the window of Stack #1 (which is the standalone)? > > As always, advice is gratefully appreciated. > > Thanks, > Barry > > _______________________________________________ > use-revolution mailing list > [EMAIL PROTECTED] > http://lists.runrev.com/mailman/listinfo/use-revolution
Try, if needed : Instead of close stack "stack #1", close window the short name of "stack #1" -- Bien cordialement, Pierre Sahores Serveurs d'applications & bases ACID SQL Penser et produire l'avantage comp�titif _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
