Hard CASE: cracking the nut?
stephenREVOLUTION2 at barncard.com
Wed May 26 12:44:16 CDT 2010
One cannot 'set the script of' inside a standalone. But perhaps a script of
a stack outside the app could be written to by a SA. ( Richmond: please let
I know in HC I would 'point' to various fields and get past the 30k limit
of their field system. However, I don't remember how I put them in the path.
I think I had some kind of handler switching system. That was over 20 years
Is script swapping really necessary? We've got so many ways to do things,
substacks, etc without the workarounds we had to do in HC. Is there really a
reason to 'do' more than a few lines?
I'm sure that "do'ing" runs slower, too, so not good for repetitive tasks.
On 26 May 2010 10:29, Richmond Mathewson <richmondmathewson at gmail.com>wrote:
> A while back Scott Rossi wrote:
> "Maybe because standalones have an (editable) script limit of 10 lines,
> meaning you can't build scripts dynamically in standalones that exceed
> 10 lines. There is no such limit in the IDE."
> seems not to, directly refer to my script problem;
> EXCEPT; my problematic script (that works in a stack, but not in a
> thread through a variety of scripts that exceed 10 lines and reside in
> Does anybody know if reffing scripts infields is interpreted as building
> scripts dynamically as they are not directly entered in the 'script space'
> of a particular object ?
> If the above is so; would I be able to circumvent the need to store
> scripts many times over in each object by stroing a script as a custom prop
> an object than can be reffed from other objects (why do I get a funny
> that scripts stored in custom props can only be accessed by that particular
> How about storing the script in the stack / card script and calling it????
> How about running down the main street with a plastic bag on my head
> "noodly, noodly, noodly, pip, pip, pip, poop" ?
> sincerely, Richmond Mathewson.
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode