On Thursday, August 7, 2003, at 02:42 AM, jbv wrote:
I know that this limitation will cause of to rewrite sections some of my existing products.
I remember in HC and OMO using scripts of controls to hold data. In case scripts of controls in MC are used for the same purpose (holding data, and not executable code), could custom props be a nice workaround ? Just asking, as I've never used custom props much...
You bring up a point I did not think of till now. Saving small snippets of data in a script is the only way to save encrypted data in a stack. Data in a custom property can be viewed. I know there are other ways to encrypt data, but this is a nice simple way.
In my case, I usually am updating code to controls with the set the script of.... There is no other way to use the same control with new code. You will have to literally replace the entire old control with a new one that is stored on an "update" card. I do this now when the control that needs to be replaced has more than 10 lines of code anyways. It goes something like this:
1. Version 1 "standalone" of a product makes a particular document.
2. You find bugs or better ways of doing something. So you update the script in those controls. You have a replica of each of those controls that get updated in the new standalone on an "update" card that the user never sees.
3. User downloads version 1.1 of standalone. Opens up their save doc in new version and the standalone recognizes that they have a version 1 doc. It updates their doc by replacing all the old controls with the updated versions from the new standalone.
Losing the set the script of .... will take away the ability to easily update a card & stack script.
Best regards, Mark Talluto http://www.canelasoftware.com
_______________________________________________ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard
