> Is there a way to control in which cast these commands create the new member? > > I'm trying to store user's work in a "storage" cast by creating a new cast > member for every chunk of user's work (a paragraph of formatted text). When > the user wants to save the work to disk, I let him save the cast to a cst > file, for opening it in a later session. > > If there's no way to control which cast the new members go, then this isn't > a good strategy. What are the alternatives? Should I save member.rtf in a > variable/list instead? Mark and Tab already threw in a few (5, 6?) cents on this, but I would like to add a few centavos. Is it necessary to use cast members and saving the cast, when you're really dealing with strings? If it's a matter of losing the formatting, then you could write a parser that drops html-style tags in at appropriate points, and writes to a txt file (file-IO). And the reverse on import. Perhaps more work at first, but if you write the methods right, they're highly reusable. Sure, there's a bit of a speed hit, but you get the benefit of flexibility. And the speed hit on import can be minimized by parsing large files in stages. dos centavos, Kurt [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!]
