Tooltip for disabled controls
swpalmer at gmail.com
Fri Apr 5 16:57:14 PDT 2013
I like this idea too. If it is acceptable breakage as far as the
backward-compatibility goes then I would say it is the cleanest approach.
It is basically what I was trying to do with the idea of an alternate
event chain... the alternate chain being just to avoid breaking the
existing filters and handlers. Here is another idea. How about a new
interface that extends the EventHandler.. it is only a marker interface to
use with event filters to indicate that you should deliver events for
disabled controls? That way all existing Event Filters still don't get
called. Would something like that work? I haven't taken the time to think
On Fri, Apr 5, 2013 at 3:01 PM, Richard Bair <richard.bair at oracle.com>wrote:
> >> So are the CSS rules designed such that disable will still be applied,
> or will the hover rules take precedence? We'd have to try it out.
> > I've tried. As I expected, controls fully rely on the events not being
> delivered. When I deliver events to a disabled button, the button stays
> grayed, but works normally - gets highlighted on hover/armed, gets pressed
> > When I deliver the events to filters but not to handlers, everything
> looks fine on the first sight.
> I like this idea, lets continue pursuing it and see if it works out.
More information about the openjfx-dev