bobs at twft.com
Thu Nov 18 14:58:35 EST 2010
Whoops! I didn't mean the splash stack should "close itself" I meant "hide itself". Closing the "real" stack will have to have a "Quit" command at the end of anything else you do. Otherwise I think the splash screen will pop up again if you close the "real" stack. The more knowledgable among us may correct me.
On Nov 18, 2010, at 9:46 AM, Joe Lewis Wilkins wrote:
> Thanks Robert.
> Just haven't had the time this AM to tackle this as yet.
> Joe Wilkins
> On Nov 18, 2010, at 9:29 AM, Bob Sneidar wrote:
>> Hi Joe.
>> Not so tough. Make a brand new stack which will be your splash stack. Have that stack open the "real" stack and then close itself. Add your "real" stack along with it's substack as an included file in your standalone settings. Mince finely, stir in with a cup of lemon juice and compile. The mincing and lemon juice are not strictly necessary.
>> On Nov 18, 2010, at 7:35 AM, Joe Lewis Wilkins wrote:
>>> Hi Richard,
>>> My intuition told me as much, and I've been surprised at how easily I'm able to change the data in a Standalone by using an external text file and then changing the text file along the way. My dilemma, now, is that this sub-stack is already part of the standalone, so splitting it off as another stack file may not be so easy. OTOH, it may also solve an issue I now have communicating between that "sub-stack" and the main stack in the standalone. We'll see once I take a look at Sarah's tutorial.
>>> Joe Wilkins
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> 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