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
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
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
Joe Lewis Wilkins wrote:
> I'll save this approach as a plan "B"; for now, I think, I'll
> just create a brand new, expandable Main Stack that I can use
> when the user needs to create new forms. I think I can probably
> do this by just creating a dummy empty stack and, then, when I
> need additi
Hi Richard,
I'll save this approach as a plan "B"; for now, I think, I'll just create a
brand new, expandable Main Stack that I can use when the user needs to create
new forms. I think I can probably do this by just creating a dummy empty stack
and, then, when I need additional copies of a Form
Joe Lewis Wilkins wrote:
> 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.
May
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 of
Joe Lewis Wilkins wrote:
> If we create a standalone with a menu item of "New Form" and
> then implement it with a handler script in which we do: clone
> this card, will this create a new card in the Standalone, keeping
> in mind that this will be done in a sub-stack? Also, with a
> matching menu
Hi Joe:
If I understand what you're asking, the answer is yes, but the cloned card
won't be saved unless your stack exists in a file that's separate from the
standalone (standalones can't modify themselves).
You'll either need to use the splash screen launcher strategy which involves
building a s
