LiveCode Forums.

I'm surely missing something ridiculously simple, but I'm freaking out because the app is supposed to go public in a few days.

I've just added a simple splash screen (substack) as a modal dialog that includes the usual credits and copyright info, to be displayed when the app first opens and when the user chooses "About" from the app menu.

That's all fine: It displays when the app first opens and when one chooses "About" from the menu (in each case dismissed by an "OK" button rather than a timed display, so the user has enough time to read and take note of the contact info).

The thing is that when one clicks on a button on the current card of the mainstack to display a different modal dialog (to set preferences), it displays again the splash screen first. (Curiously, this doesn't happen when one clicks on a different button that summons an "ask file" dialog.)

I've tried placing the command "modal stack "Splash" " in either preOpenStack or openStack messages in the mainstack script, but neither makes a difference. I don't know where else to put this so the splash screen isn't displayed after the app is opened unless called from the "About" menu.

Any advice will be greatly appreciated.

jeff k

Hi. Not at a computer right now, but dies moving the handler to an openCard handler in the card script of the first card of the “main” card help?

At least there the handler will be localized, thought it also reduces it availability. But these things are usually only accessed at the opening of an app, where it will indeed be seen.

Craig Newman

When the prefs modal stack opens, preOpenStack and preOpenCard messages are sent, which your mainstack catches and executes the splash display. Do what Craig suggested and move the preOpen-whatever handler to the first card of the mainstack where it won't be triggered by any other stacks.

Craig and Jacque --

Thanks much for your sound advice, which I will implement in v. 1.01 of the app. I know that it's poor form in LC (or any language) to rely upon kludges, but in the meantime I've resorted to employing a custom prop to work around the problem:
It's ugly, but -- being under deadline -- it seems to work as a temporary solution.

Best,

jeff k