[Wayland-bugs] [Bug 103054] Debouncing active but no effect
https://bugs.freedesktop.org/show_bug.cgi?id=103054 Peter Huttererchanged: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WONTFIX --- Comment #5 from Peter Hutterer --- yeah, basically that's the problem. Timeouts are the only way we can detect these false clicks but if the timeouts go too close or above what you would otherwise trigger by manually clicking (which can be in the ~20ms range) then you start getting stuck buttons. If you get 64ms for those fake clicks, there isn't really anything we can do and you're really better off getting a new mouse. Anything else would require putting special behaviours in that you then have to train yourself to stick to. Not really worth the effort because it's still likely going to be unreliable. So sorry, I'm going to have to close this bug. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 788497] GdkMonitor geometry & workarea are not returned in application pixels with GDK_BACKEND=wayland
https://bugzilla.gnome.org/show_bug.cgi?id=788497 Robin Burchellchanged: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Robin Burchell --- Yeah, I suppose it's fine to handle it there then. *** This bug has been marked as a duplicate of bug 783995 *** -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 103054] Debouncing active but no effect
https://bugs.freedesktop.org/show_bug.cgi?id=103054 --- Comment #4 from mrbloo...@hotmail.com --- Created attachment 134663 --> https://bugs.freedesktop.org/attachment.cgi?id=134663=edit Longer evemu-record log I have increased the time to 16ms, but I still experienced double-clicks. Then I recorded the events for a longer time and checked again. I'm not sure if I'm looking at the time for the right event, but I noticed on some double-clicks it goes up to 64ms (line 3048 in the attachment). Am I looking at the correct event? After that I increased it again from 16ms to 64ms and the double-clicks seemed to have stopped. However, I experienced another issue, where it would start dragging the directory. I think that 64ms is too high and interferes with desired events? I assume some mice with inconsistent and too high delays between false clicks can't be fixed this way? Either way, thank you for the help. I guess this is RESOLVED now and can be closed. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 788497] GdkMonitor geometry & workarea are not returned in application pixels with GDK_BACKEND=wayland
https://bugzilla.gnome.org/show_bug.cgi?id=788497 Olivier Fourdanchanged: What|Removed |Added CC||ofour...@redhat.com --- Comment #1 from Olivier Fourdan --- Reminds me of bug 783995 -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 771112] some applications windows to grow on startup (with CSD)
https://bugzilla.gnome.org/show_bug.cgi?id=771112 Daniel Boleschanged: What|Removed |Added Status|NEW |RESOLVED CC||dboles@gmail.com Resolution|--- |NOTABUG --- Comment #16 from Daniel Boles --- It looks like there's not any actual bug here. The outstanding one was probably the concerns about the docs mentioned in Comment 11, but Emmanuele seems to have fixed that the next day with commit 08e443e0db6f74ade5836f8028073aeac14aab38. So, resolving as NOTABUG (in GTK+) (anymore)! -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 788497] New: GdkMonitor geometry & workarea are not returned in application pixels with GDK_BACKEND=wayland
https://bugzilla.gnome.org/show_bug.cgi?id=788497 Bug ID: 788497 Summary: GdkMonitor geometry & workarea are not returned in application pixels with GDK_BACKEND=wayland Classification: Platform Product: gtk+ Version: unspecified OS: Linux Status: NEW Severity: normal Priority: Normal Component: Backend: Wayland Assignee: gtk-b...@gtk.org Reporter: robin+gn...@viroteck.net QA Contact: gtk-b...@gtk.org CC: r...@robster.org.uk, wayland-bugs@lists.freedesktop.org GNOME version: --- Created attachment 360895 --> https://bugzilla.gnome.org/attachment.cgi?id=360895=edit GtkMonitor: Fix geometry and workarea geometry on high DPI screens on Wayland See attached patch (based off gtk-3-22 branch). I haven't yet tested this (busy with dayjob stuff), but I stumbled across this when working on gtkplatform. GDK_BACKEND=x11 reports correct values. I'm quite certain that this is a valid bug regardless of the correctness of my fix, so figured I'd file it while I still remember that it's a problem. I'd really like this to be fixed in a 3.x release if possible. -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 788420] Wayland: Too wide windows/subsurfaces cause exit
https://bugzilla.gnome.org/show_bug.cgi?id=788420 --- Comment #7 from Olivier Fourdan--- Wouldn't that be leaking a compositor/backend implementation/limit onto the clients (for example, the same works with "weston --use-pixman")? -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs