David Bovill wrote:
> For most situations this is not a problem, as most scripts are called from
> controls. I just happened to have a stack where I used the card script - and
> voila no background scripts get intercepted!
>From the MC docs:
"Messages not handled by an object are passed up the object hierarchy
until a handler for that message is found. Messages sent to controls in
groups pass from the control, to the group, to the card, to the stack,
to the mainStack (if the stack is a substack), and then to the Home
stack. Messages sent to controls on the card are passed from the
control, to the card, to each of the backgrounds (groups) on that card,
to the stack, to the mainStack (if the stack is a substack), and then to
the Home stack."
This would imply that a card script will have access to and will share
background scripts with each group (provided the message didn't come
from a control within a group) -- but there could be a problem as the
message gets sent from one group to another. If each group has a handler
with the same name, the message will stop at the first group containing
the handler. If you intend for the message to be sent to a different
group, then it won't get there.
--
Jacqueline Landman Gay | [EMAIL PROTECTED]
HyperActive Software | [EMAIL PROTECTED]
Custom hypermedia solutions | http://www.hyperactivesw.com
612.724.1596 | 612.724.1562 - fax
Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
