Le 4 août 09 à 01:35, stephen barncard a écrit :
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.
I have tried the "insert" command (in back) in place of "start using"
and it seems to work OK on my lil' test stack.
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...
yes, I have used it to check the attached stack in the IDE.
Thanks for your quick answer.
Cheers,
François
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
