-
|
So, we have But they have a limitation. Use I mean, arguably, I would be fine except when I do: I would expect that the mouse_over would be the current widget directly beneath the mouse, however it isn't. It's the widget that I just removed. In fact, generally, moving the mouse around won't track any mouse events on any of the lower widgets, just the one that is currently under the mouse. I had hoped that changing it to call_later would help: But alas, it doesn't. It still reports the widget that the mouse had been on. I can add which will give me the point on the screen, and there is this answer/discussion which seems to have an option for detecting the widgets that are at a particular location on the screen... Is there any better way to do what I'm trying to do here, which is to say, detect the widget(s) that occupy a screen location? (I can use the widget ID to figure out if it's the one that I want) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Ahah! I had searched the docs for I knew the |
Beta Was this translation helpful? Give feedback.
Ahah! I had searched the docs for
_atandlocationand a whole bunch of other terms that didn't get me anything. I decided to Use the Source, Luke, especially since I already had the source locally so I could check out the demo code.I knew the
mouse_overattribute existed so I went and found where that was, which led me to a few places ending up at theget_widgets_atfunction. That actually gives me exactly what I need: