If you leave out the first handler, Beat, other controls that DON'T
override the behavior will get no mouseUp behavior at all!
George
On Oct 26, 2009, at 2:37 PM, Beat Cornaz wrote:
Thanks for your answer Trevor. It works good. I found that it can be
even 'easier' :
The first part (on mouseUp pBtnNum) of the Behavior Script is not even
needed.
===============
Behavior Script
===============
on mouseUp pBtnNum -- This handler can be left out.
_mouseUp pBtnNum
end mouseUp
command _mouseUp pBtnNum -- This handler alone will do the trick
DoA
end _mouseUp
----------------------------
I start to get the idea of behaviors. They behave like commands or
functions, but can be accessed from everywhere and are restricted to
act only in response to certain objects (the ones with that behavior
assigned) with a certain message (like mouseUp).
So the commands and functions can be more specific, less general than
say in a library . Great.
Thanks,
Beat
_______________________________________________
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
