Thanks to Mark and Phil;
I get what you are saying here, there is a preopen stack event in the
main stack, which it is going to hierarchically go back to, and
execute, because we happen to be opening a stack, and there is no
specific preopen stack for THIS stack. I put in a blank preopen stack
for this and it trapped it and did what I was wanting.
I appreciate the help!
Jim McNeely
On Sep 16, 2008, at 10:52 AM, Phil Davis wrote:
Hi Jim,
What you experienced here is normal behavior. In Rev's message
path, the mainstack's stack script is always between its substacks
and the engine. So if you don't want those substack 'open' messages
to be handled by 'open' handlers in the mainstack, you could do any
of several different things, depending on your requirements:
- in the "PatientFind" stack script, you could put:
on preOpenStack
-- trap the message
end preOpenStack
- or in the button script that opens the substack you could put:
on mouseUp
lock messages
go to stack "PatientFind"
unlock mesages
end mouseUp
I'm sure there must be other ways to prevent your unwanted
outcomes, but these will get you going.
HTH -
Phil Davis
Jim McNeely wrote:
Another newbie question; I appreciate the patience and help.
I have this attached to the main stack:
on preOpenStack
put revOpenDatabase("mysql", "localhost", "blechy", "account",
"pw") into MySQLID
answer "MySQL connection ID: " & MySQLID
end preOpenStack
THEN, I have a button which is supposed to open a substack window
thusly:
on mouseup
go to stack "PatientFind"
end mouseup
When it opens PatientFind, it executes the main stack's on
preOpenStack script, and then, if you close that window, it wants
to know if you want to save the changes to the whole file.
What's up with that? I've read all the documentation I can find
about stacks and substacks and cards and such, and none of it
hints at this behavior.
TIA,
Jim McNeely
--
Phil Davis
PDS Labs
Professional Software Development
http://pdslabs.net
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
