question dialog nested in a messagebox?

[Wooden Brain]

I remain a bit confused by all these pushing widgets in Salling 3.0.

Here's a specific thing I'm stuck on. I want to display some text as a message box, and then after the user hits ok show a yes / no dialog. i can do either of those things individually, but the responses to both are handled by a "process dialog ok" handler.

I assume that there can be only one "process dialog ok" in the script. But the yes/no dialog would have to be called within that, and there would need to be a way to know WHICH widget/dialog resulted in that handler being called. The process dialog ok handler takes an argument, but does that refer to the widget being pushed, or to the terminal, or .... doh i'm confused.

edit: off topic here, but suggestion -- allow use of 5 way nav on palm to scroll messagebox text fields up and down. problem -- if messagebox left too long without pressing OK, seems to get stuck, any keys then just beep. timeout option might also help.

[salling]

You're on the right track.

The widget passed into the "process dialog ok" handler is the widget being dismissed. All you need is an if/elseif construct to determine which widget sent the event. You can use the "name" property of the widget base class to identify widgets.

As for the other problem, are you connecting over Wifi by any chance?

Best.
--
Jonas

[Wooden Brain]

edit:

I got it to work. instead of using "tell a_terminal" with a_terminal defined as a global variable, withing the process ok handler, I use "tell terminal of a_dialog". It works, but the other way should work too. all of these widgets and terminals and such should be able to be global variables, not just their names or IDs. I'm not sure frankly how much of an improvement this new method is -- I think I liked the "mode" of 2.x better. But maybe I'm just not used to it yet. It seems to be a lot more advanced, though.

--WBC

original msg:

thx, jonas. no luck so far. first of all, i apparently can't use the name property of a widget to identify it, at least not without setting a name first. id seems better. but this still doesn't work. i get the first message ok, but not the follow up question. first of all, i apparently need to define global variables. second of all, what am i telling? if i tell a_terminal for the question dialog (assuming you have to tell the SAME terminal, defined globally), then I get a variable a_terminal is not defined error. If I leave out that tell block, surrounding the make question, then I get an NS ArgumentsWrong error.

global messid, questionid, a_terminal

using terms from application "SEC Helper"

on process invoke a_terminal
tell a_terminal
set the_widget to make new messagebox dialog
set messid to id of the_widget
set textual content of the_widget to messid
push the_widget
end tell

end process invoke

on process dialog ok the_dialog
set wi to id of the_dialog
if wi = messid then
show screen message ("ok to message")
tell a_terminal
set the_question to make new question dialog
set textual content of the_question to "Test yes no"
set questionid to id of the_question
push the_question
end tell
else if wi = questionid then
show screen message ("ok to question")
end if
end process dialog ok

on process dialog cancel the_dialog
show screen message "No/Cancelled"
end process dialog cancel

end using terms from

as for the other question, yes i'm using wifi.

[salling]

Hi,

Global variables are potentially very bad if multiple terminals are connected to the same script. The way you describe doing it (the way that works) is exactly how it's to be done.

Best.
--
Jonas