Thanks to Mike Bonner for his helpful suggestions. Stack A and Stack B are both
mainStacks. Further tests seem to confirm this rule:
A setProp or getProp handler in the script of stack A cannot be invoked for a
target in Stack B UNLESS we have "started using" stack A (even if Stack A is
Hmm. Ok. My mistake. Seems to work.. is stack B a substack of stack A? If
not, that might be the issue.. If stack b is a mainstack, then the request
can't go up the message path to stack a, which then makes my previous point
applicable.
On Sun, Sep 11, 2016 at 3:59 PM, Mike Bonner wrote:
> The
The "of stack b" part, delineates where the pseudo property resides. Since
there is no getprop nSL of stack b, you get nothing back. Better off to
create a function that takes an object reference as a parameter, and make
sure its in the message path so you can hit it from anywhere.
On Sun, Sep 11
The script of stack “A” has a getProp handler to report the number of lines in
an object’s script:
getProp nSL
return the number of lines in the script of the target
end nSL
With stack A frontmost, I type in the message box “the nSL of this stack” or
“the nSL of stack’A’”, and I get the expec
