I'm finding that I have to do things like track the Window state and mouse location to get the tooltip displayed correctly. I'm on Linux which sometimes displays popups like menus incorrectly, like wildly off the Stage

Too bad you have to deal with this manually.. Maybe you could fake it somehow instead? Having a button that has a disabled style, but is not disabled perhaps.

@edvin yeah. i could go that route, but I'm really attached to the disabled binding statement that I coded

@carlw Post the code when you're done, maybe we can come up with something!

sure. should be ready in a little while.

It seems a little strange to me that disabled kills all events like mouseover

At least it's documented "A disabled Node does not receive mouse or key events."

I apologize for the Java...

Hehe 🙂

I have to step away for a little bit, will check in soon.

@User uploaded a file: Wrapping Control for Disabled Tooltip

@edvin I'm going to do a double-blog on this for both Java and Kotlin. Maybe we can reprise the live code review?

This gist of this code is that I use an event filter (not handler) on the control's container since the control itself won't generate any events.

@carlw Would it be possible to call

button.fireEvent()

and passing in a fake MOUSE_MOVED event when it's disabled?

@edvin Who would call button.fireEvent()?

@carlw Your listener on the parent?

If that's possible then maybe you don't need to do all the other house keeping manually.

i don't think it's listening to anything...i'll try to chain the VBox's mouse moved to a button.fireEvent()

you want me to just pass it MOUSE_MOVED or a fake event?

It must be MOUSE_MOVED, and I guess you need to send the correct coordinates even. Do you know what code removes the listeners? Maybe that could give us some ideas. Is it the ButtonSkin?

i'm not up-to-speed on skins since I got burned using Sun Skins with 2.2 (they broke in 8)

it looks like I can deliver a mouse moved event. i used a setOnAction in another button to call button.fireEvent()

i'm going to push it to github and test on windows and mac

So you can avoid all the manual setup of the tooltip? That's great!

I'm not following your suggestion on firing the event. I'm not doing anything with the tooltip setup, just creating the delayed activation and cleaning up when i leave the control.

OK, I think we're misunderstanding each other. My theory was that you could listen for mouse move events on the parent, and when you determine that the mouse is over the area for the disabled button, you fire that mouse move event on the button so that it would show it's tooltip.

I have the event filter on the parent and a bounds check to see if it fired within the disabled control. I'm not sure if the tooltip fires on a simple mouse move though

If we can find the code that enables the button we don't need to guess. I'll see if I can locate it.

ok. i'm going to send a mouse move to an enabled button and see if it activates a tooltip

I found the code. To successfully fake those signals you need to catch and resend MOUSE_MOVED, MOUSE_EXITED, MOUSE_PRESSED.