[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gambas-bugtracker] Bug #2886: wayland and Mouse.ScreenX & Y, Top-level?
[Thread Prev] | [Thread Next]
- Subject: [Gambas-bugtracker] Bug #2886: wayland and Mouse.ScreenX & Y, Top-level?
- From: <bugtracker@xxxxxxxxxxxxxx>
- Date: Fri, 19 Apr 2024 19:56:42 GMT
- To: bsteers@xxxxxxxxx,bugtracker@xxxxxxxxxxxxxxxxxxxxxx
http://gambaswiki.org/bugtracker/edit?object=BUG.2886&from=L21haW4- Comment #3 by Benoît MINISINI: > So there is definitely no mistake then? > Mouse.screenX and ScreenY can be considered useless/broken with Wayland. Mostly yes. Not always useless, as the GUI toolkits normally returns in Mouse.ScreenX and Mouse.ScreenY the coordinates of the mouse cursor relative to the (activated?) window. > And there is no way to get main form/window positions correctly? No. All top-level windows are seen at coordinates 0,0. The only exception in Wayland are sub-surfaces, i.e. windows that are told Wayland to be children of another windows. In that case, the sub-window has coordinates relative to its parent. They added that so that implementing popup windows becomes possible. Benoît MINISINI changed the state of the bug to: Upstream. ----[ Gambas bugtracker-list is hosted by https://www.hostsharing.net ]----
[Gambas-bugtracker] Bug #2886: wayland and Mouse.ScreenX & Y, Top-level? | <bugtracker@xxxxxxxxxxxxxx> |