LiveCode Forums.

Hi Friends!

Is there some sort of way to process things when a user attempts to leave a card, such as a PreCloseCard handler that I can exit from without closing the card? I read in the Documentation that trapping the CloseCard message does not affect navigation.

Basically, I have a card that has a form on it. If the user leaves the card, but has not clicked the Submit button, I want to prompt them and ask whether they are sure they want to leave the card. If they do, proceed. If not, though, I want the card close behavior to break.

This is probably pretty obvious, but I wasn't able to turn anything up in the Documentation.

Thank ye!
Phil E.

What is the action that causes the card to change in the first place?

Maybe you can have an if statement that says something like this,

Hi Phil,
I think you may have over thought this.
How does the user leave the card?
A button?
Your button?

I haven't tested intercepting "on closeCard" I'll take your word for it. But what calls it?

Simon

LiveCode supports a closeStackRequest message because there's at least one action (clicking the window's close box) which could trigger a close over which we have no control in our scripts. Similarly it also has a shutDownRequest message for when any action is taken which could cause your app to quit, which may even be initiated by actions outside your app.

But as William Jamieson suggested, with card-to-card navigation within a stack we normally have complete control over actions that would cause the user to leave a card, where you can do any checking you need before proceeding with the "go" command.

That said, I find the notion of a closeCardRequest message intriguing. Can anyone here come up with use cases where it would be a solution not solvable by other means?

Might it be used, as the other "...request" messages are, to prevent card navigation?

The "closeStackRequest" message is not sent if the user executes: "close this stack" from a handler. But "closeCard" is sent, so that should not matter.

Craig