If you try to navigate the dashboard using the arrows on the keyboard and the mouse cursor happens to be on a point where it can change the selection of the grid, the selection comes back immediately to the element where the mouse cursor is. This makes impossible to navigate the grid only with the keyboard until you put aside the mouse cursor on a place where it can't toggle the selection of any element of the grid. This problem doesn't happen on the filter list on the right of the dashboard, if you put the mouse cursor over the list you can navigate the list normally and the selection only changes if you move the mouse. How to reproduce: 1.-Open the dashboard. 2.-Put the mouse cursor on any place where it can highlight any element of any of the grid views of the dashboard. Current behavior: If you try to navigate the grid with the arrows of the keyboard the selection comes back to where the mouse cursor is. Expected behavior: Even if the mouse is highlighting an element of the grid if you should be able to navigate the grid with the arrows of the keyboard and the selection should only change if the user moves the mouse.
This must be a bug either in MouseEventListener or in Qt - it's happening because after every keyboard event, MouseEventListener.onPositionChanged fires (with unchanged coordinates).
I think this is a deliberate change in Qt so mouse position / hover state is re-evaluated if the item changes underneath the mouse without the mouse moving. I had the same issue in KRunner where suddenly it would select results under the mouse as you typed.
Thanks a lot for your answers. If you need for me to do anything that can help you just tell me.
Kai: How did you solve it in KRunner? I can cache and compare the coordinates locally but holy fuck writing "did the position actually change in this onPositionChanged" code is frustrating.
See https://phabricator.kde.org/D5490
Can we move MouseHelper somewhere generic then so we can reuse this in Dash?
*** Bug 383033 has been marked as a duplicate of this bug. ***
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. 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. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!