Nuts.
The issue has re-emerged again today. As before, with this in the stack script of a substack:
Code: Select all
on closeStackRequest
save stack "shapes"
close stack "shapes"
end closeStackRequest
A handler in the mainStack that navigates to that subStack will indeed go there, but then execution stops at that line. However:
1- If the subStack is already open, then the mainStack handler works just fine all the way to its end.
2- If I comment out the above subStack handler, then the mainStack handler works just fine all the way to its end.
I have ways around this, I just don't get it. What on earth has a closeStackRequest in a subStack have to do with the mainStack handler? Did I mention that a breakpoint in the closeStackRequest never fires?
A brand new stack/substack with a navigation handler in the mainStack and the above handler in the substack works just fine. I am not surprised, just nuts.
So there is something about my project stacks. Shocking, I know. But how do I find out what, if no breakpoint ever fires? In other words, what is the difference between a handler that is never used, and a handler that does not exist at all? How do it know?
Craig