Bonjour,
I had such problems recently. Behaviors property still set when
reopening stacks but not inherited.
It was with rev 4.0.
See subject "Behaviors handlers not found when re-opening stacks" in
the June' archives
Trevor reply with this address :
http://quality.runrev.com/qacenter/show_bug.cgi?id=8280
So I shifted to Rev 4.5 and it works now
Don't if that helps
Best regards from Grenoble
Le 22 juin 10 à 23:19, [email protected] a écrit :
Mark.
Yep, you're right. If I quit rev and reopen, and immediately ask for
the
behavior of the stack, I get a valid button reference. So it seems
like
everything should be fine. But no go, like you discovered. And yes,
if I set the
stack behavior manually all over again, changing, ostensibly
nothing, it
works.
I'm going to report it.
Craig
In a message dated 6/22/10 4:54:21 PM, [email protected] writes:
That would be nice. But I'm finding that it doesn't work that way. It
seems ok while the stack is still in memory after I've set the
behavior, but if I save a stack with the stack behavior set to a
button with a preOpenXXX or openXXX or all the above and then reload
it, the messages aren't caught by the behavior button. If I set the
card behavior to the button then the message *are* caught when the
stack reloads.
_______________________________________________
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
