On 10/11/06 5:23 PM, "Trevor DeVore" <[EMAIL PROTECTED]> wrote:
On Oct 11, 2006, at 11:03 AM, Ken Ray wrote:
Actually what I mean is that it shouldn't act like it doesn't
exist... if
you click on a disabled opaque button, it shouldn't pass the click
to things
behind it...
Ah. I could see how you could make an argument either way but like
Malte I have come to rely on the current behavior.
I think where I'm coming from is that none of the other xTalks I've used
(HyperCard, SuperCard, Oracle Media Objects, etc.) behave this way, so to
me
it seems "wrong". I wouldn't want to suggest that it should be changes to
break other people's code, but perhaps some way to make it not do that (a
new global property, a new object property, etc.) would be nice.
Logically, I think this is a bug. When clicked, a disabled button should by
definition NOT do anything, lest of all pass a click to any other object.
Cheers,
Kevin
_______________________________________________
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
