Scott Rossi wrote:
I assume that card-level behaviors
should "fall through" to stack-level behaviors, but weirdly, I got script
errors saying the handler/function couldn't be found. I tried a simple test
stack and stack-level behaviors appear to work there, so I can't figure out
what's going on.
I just getting into behaviors also, I'm curious to better understand
what you are doing and what works and what does not.
I thought a behavior was placed in an object (typically a button,
right?) and then you set the behavior of whatever other object (the
stack in your case?) to the long ID of the object that has the behavior
(the aforementioned button)
Now, I'm not sure what you mean by "card-level behaviors falling thru to
stack-level behaviors" but from one point of view it makes sense that
the behavior cannot be found, because the button that contains the
behavior is not really in the message path as we normally understand the
message path. In fact, I could have sworn that the nature of behaviors
not being in the message path was part of their "charm" so to speak...
i.e. you would deliberaty keep certain handlers segregated from the msg
path by having them be behaviors.
Of course, I really don't know what I'm talking about so take all of the
above with a grain of salt.
Sivakatirswami
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
