Alternatives to "answer"
bobs at twft.com
Fri Apr 29 18:51:47 EDT 2011
Use the dialogData. You can set it to whatever you want in the "dialog" stack, and then retrieve it in your main stack. The dialogData is a global property you can set and get throughout the IDE or runtime environment.
Also make your stack modal, meaning it must be dismissed before the user can click anywhere else.
Don't call a procedure in an unopened stack (unless it's script has been inserted into the frontScript or backScript, and that still doesn't open the stack to display the card. You still have to GO to the stack to do that.)
That no workie nohow. Just go to the stack and have the openStack handler of your "dialog" stack call whatever procedure you have, or just have the openStack handler BE the procedure.
On Apr 29, 2011, at 3:37 PM, tbodine wrote:
> Hi LiveCoders.
> I'm working on my first real LC project and now I've dug myself into my
> first LC hole. Hoping for some advice...
> I want to present user with a dialog box that is more attractive than the
> standard "answer" command. (Bigger type, transparent, icon buttons). I tried
> making a separate card in a separate stack that I could open over my
> mainStack card, but that is creating lots of errors now with "can't find
> card" messages when I use:
> call processingHandler of card "Main" of stack "Top".
> Basically, I want a semitransparent dialog box with two buttons to open over
> a mainStack card. The user's button choice needs to be returned to the
> mainStack script and the dlog Card closed.
> Any suggestions on how to do this?
> Tom Bodine
> View this message in context: http://runtime-revolution.278305.n4.nabble.com/Alternatives-to-answer-tp3484779p3484779.html
> Sent from the Revolution - User mailing list archive at Nabble.com.
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode