Summary: | Strange Behavior Under Wayland | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | ybx332 |
Component: | ux-ui | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | ldoktor |
Priority: | NOR | ||
Version First Reported In: | 5.1.2 | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
ybx332
2022-05-31 11:34:14 UTC
Is this a possible duplicate of bug #446990 ? (In reply to Thomas Baumgart from comment #1) > Is this a possible duplicate of bug #446990 ? Partly. The date problem is related to that. But the calculator problem isn't. The calculator problem is that the calculator itself will not pop-up at the right place, Instead, each time I need to click it twice to make it pop-up at the right place. The first time I click it it will just pop-up at the left corner of the screen. Is this still valid with 5.2 or newer? Does KMyMoney have any control over where the calculator pops up? My reading of the code shows it doesn't even try, so the location would be system dependent. If I click the calculator button more than once, I get a new calculator (always center of the screen for me, using Wayland) for each click. What do you mean by "the right place?" KMyMoney positions the popup relative to the basewidget (date or amount widget) using its PopupPositioner object (https://invent.kde.org/office/kmymoney/-/blob/master/kmymoney/widgets/popuppositioner.cpp). Unfortunately, this does not seem to work either with Qt6 or Wayland (since the call to mapToGlobal in line 27 always returns the relative position to the application window). Others (see https://www.qtcentre.org/threads/50737-Can-t-seem-to-get-global-screen-position) seem to have the same problem to figure out the global position of a widget. ๐๐งน โ ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! ๐๐งน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |