Geoff Canyon
Sun, 17 Sep 2000 23:56:44 -0700
on 9/17/00 5:29 AM, Raymond E. Griffith at [EMAIL PROTECTED] wrote: >> 2. Edit the old stack as a pure text object. Obviously this is tricky, not >> recommended, perhaps not possible at all, possibly a violation of the >> license agreement, and in general Not A Good Idea. But it would certainly >> not produce the script limits problem your current method does. >> >> gc > But this will not work for two reasons. First of all, the stack is binary, > not text. Editing as text means also saving as text, thus destroying the > stack. Even if your stack has a .txt ending, it is still written as a > binfile. I misspoke saying text, but I believe it _is_ possible. Open the standalone builder to see how. The only roadblock I see possible is if MetaCard stores internal references to the length of a script, for example, that might need to be updated at the same time. Stack integrity could be an issue. > > I tried opening a stack I had so edited. Kablooey. > > And even so, there are some things that should not be done wrg the license > agreement. If changes in the stack's script need to be done so that the > scriptlimits are not violated. > > And there *are* ways to legally handle scripting with the unlicensed version > so that you are doing everything you want to do. I know. I have been doing > it for some time. I never violate the scriptlimits, yet I can do a great > deal. Basically it involves placing code in non-script places, as custom > properties, and running them with do statements. The scriptlimits also apply to do statements, I believe. But Scott, isn't this whole conversation moot? I thought the licensing limitations were to limit an end user's ability to add their _own_ code, not to prevent them from applying a patch that a licensed developer provided them? >There are also other > techniques. If you want to know more, start a new thread and ask. > > One other suggestion. Create the stack with other stacks as plugins that > your main stack accesses. You can upgrade the plug-in. This last is certainly a good suggestion. gc Archives: http://www.mail-archive.com/metacard%40lists.best.com/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to <[EMAIL PROTECTED]>, not this list.