Message path and standalones

stephen barncard stephenREVOLUTION2 at barncard.com
Mon Aug 3 19:35:27 EDT 2009


The 'splash screen method' is indeed a wonderful feature of Runrev,
especially in a Macintosh standalone. And yes 'start using' works fine in a
standalone.
But the path strategy is different for a standalone than working in the IDE.
 The paths have to be specified in relation to the stack engine, not the IDE
engines and externals in their normal places on your drive.

I won't run down the exact sequence of how to do it, but  a couple of clues:

use the 'effective filename of this stack' to get your standalones' location
(from within the running standalone code)
and set the location of the stacks to include relative to that. Relative
addressing works.

ALSO

remember you can
open up the .app package and WORK DIRECTLY with those stacks in the
IDE,   You don't have to rebuild the standalone each time,
unless you add externals or need to add features from a newer version of
Runrev that wasn't there before.

Not only can you edit, compile and run, you can also FIX stuff. And you can
leave the IDE idling while you test in the standalone.

 It's the speediest, easiest way to work.... for me at least...


-------------------------
Stephen Barncard
San Francisco
http://barncard.com


2009/8/3 François Chaplais <francois.chaplais at mines-paristech.fr>

> I am currently trying to compile my stack(s) into MacOS X standalones. This
> is rev studio 3.5 gm2.
> I am trying to use the "Splash page" inplementation for the standalone.
> I am looking for confirmation and, if possible explanation for the
> following facts
> a) start using stack etc... does not seem to work in a standalone, i.e.
> handlers that should be in the extended message path are not executed. I can
> reproduce that on an elementary stack.
> b) send (message etc...) to the proper object works
> c)  handlers which are not in the message path in the are not detected in
> the IDE at compile time, but only at runtime. Wouldn't it be nice if this
> could be detected at compile time?
>
> Finally, I have not tried behaviors and I would be glad if I could get some
> info on their "behavior", so to speak, in a standalone with multiple stacks.
>
> cheers from Paris
>
>        François
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>



More information about the use-livecode mailing list