Hi Ken,
I agree and disagree at the same time:
A disabled button is a disabled button regardless of any of its other
properties.
But, when it's disabled, should it not exist as it's the case now.
I think you are right: the answer is no :-)
Best Regards from Paris,
Eric Chatonet
Le 11 oct. 06 à 19:02, Ken Ray a écrit :
On 10/11/06 11:55 AM, "Lars Brehmer" <[EMAIL PROTECTED]> wrote:
I just wrestled with a problem, finally solving it by trying
something that in my opinion shouldn't be necessary, but why this was
necessary makes no sense to me whatsoever. Can anyone explain this?
Yes, it's a bug (IMHO)... :-)
The reason I say this is that the button's "opaque" property should
control
(once again, IMHO) whether mouse clicks are trapped. Since a
disabled button
has its opaque property still "true" means that it should continue
to trap
mouse clicks. The fact that it doesn't tells me it's a bug.
So unless there's some dissenting opinion on this, I'd recommend
logging
this as a bug in Bugzilla.
Ken Ray
Sons of Thunder Software
Web site: http://www.sonsothunder.com/
Email: [EMAIL PROTECTED]
------------------------------------------------------------------------
----------------------
http://www.sosmartsoftware.com/ [EMAIL PROTECTED]/
_______________________________________________
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
