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
My hardware is compatible and my graphics drivers are up-to-date.
What happened?
There is an issue with the current version of rust-windowing/winit that prevents touch support from functioning properly in Wayland (see rust-windowing/winit#1996). Tapping a button will not correctly fire the button's on_press message since iced_winit isn't receiving correct location data. I found that if I touched the button, moved my finger along the button, and then released, the button would function properly.
A fix has been merged into the winit upstream that fixes this issue. The fix is currently unreleased and I'm not sure what the timeline on it is. I forked iced-rs/winit and cherry-picked the PR since I don't want this issue to delay my hobby project, and I can confirm that this PR fixes the issue I was experiencing.
The reason I'm posting this is to add to the knowledge base regarding this problem. This had me stumped for a few hours today.
What is the expected behavior?
Expect button tapping to fire the button's on_press message.
Version
0.4
Operative System
Linux
Do you have any log output?
No response
The text was updated successfully, but these errors were encountered:
I am on 0.12.1 (which would have winit=0.29), and I still have this issue. Running Weston, weston-simple-touch works perfectly, however my iced application does not fire on_press correctly.
Is there an existing issue for this?
Is this issue related to iced?
What happened?
There is an issue with the current version of rust-windowing/winit that prevents touch support from functioning properly in Wayland (see rust-windowing/winit#1996). Tapping a button will not correctly fire the button's
on_press
message sinceiced_winit
isn't receiving correct location data. I found that if I touched the button, moved my finger along the button, and then released, the button would function properly.A fix has been merged into the
winit
upstream that fixes this issue. The fix is currently unreleased and I'm not sure what the timeline on it is. I forkediced-rs/winit
and cherry-picked the PR since I don't want this issue to delay my hobby project, and I can confirm that this PR fixes the issue I was experiencing.The reason I'm posting this is to add to the knowledge base regarding this problem. This had me stumped for a few hours today.
What is the expected behavior?
Expect button tapping to fire the button's
on_press
message.Version
0.4
Operative System
Linux
Do you have any log output?
No response
The text was updated successfully, but these errors were encountered: