You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From some brief debugging, the mouse move does not activate the following if-condition: if state.cursor_position != cursor_position && state.bounds != bounds {.
What is the expected behavior?
I'm expecting the mouse_area element to dispatch an OnMove message when I move the cursor over that mouse area element, but it doesn't since 0.13.
Version
crates.io release
Operating System
Windows
Do you have any log output?
No response
The text was updated successfully, but these errors were encountered:
pixelprizm
changed the title
mouse_area doesn't activate on_move message
In 0.13, mouse_area doesn't activate on_move message
Sep 20, 2024
pixelprizm
changed the title
In 0.13, mouse_area doesn't activate on_move message
In 0.13 and 0.13.1, mouse_area doesn't activate on_move message
Sep 20, 2024
Is your issue REALLY a bug?
Is there an existing issue for this?
Is this issue related to iced?
What happened?
The
mouse_area
element withon_move
seems to be broken in 0.13 and 0.13.1. It worked in 0.12.The following code dispatches the OnMove message in 0.12 but not in 0.13.
on_press
still works.It looks related to the change made here: c711750#diff-2b3d8bbc11ac699d4e936dac3b987950f3d1a63b5345395c14541a1021322e14R322.
From some brief debugging, the mouse move does not activate the following if-condition:
if state.cursor_position != cursor_position && state.bounds != bounds {
.What is the expected behavior?
I'm expecting the mouse_area element to dispatch an OnMove message when I move the cursor over that mouse area element, but it doesn't since 0.13.
Version
crates.io release
Operating System
Windows
Do you have any log output?
No response
The text was updated successfully, but these errors were encountered: