https://bugs.kde.org/show_bug.cgi?id=429177
--- Comment #3 from Duncan <1i5t5.dun...@cox.net> --- (In reply to Alexander Lohnau from comment #2) > Actually KRunner is supposed to follow the mouse, but on wayland there is > currently no way of getting the cursor position. Also there is no primary > monitor concept, which could be a workaround. I'd read about wayland lacking the primary monitor concept in other bugs. Unfortunate. As for follows-mouse, kwin as compositor has to know the mouse position, correct? And it can enforce under-mouse on other windows -- I have a kwin window placement rule that does just that for the troublesome appmenu-in-titltebar menu-popup, which otherwise follows the general least overlapping rule and ends up way across the screen -- troublesome when you have focus-follows mouse set as you can't get there without changing focus away from the window whose menu you are trying to work with. Unfortunately, apparently krunner is a plasmashell window, and plasmashell windows get to override kwin's window rules, even user-set ones! (I've seen that mentioned in other bugs.) That explains why krunner ignores the under-mouse window-rule I've set for it. If I could just find out where that ignore was coded I could try to hack-patch that out and my krunner window rule would work as it should. But so far that has eluded me. -- You are receiving this mail because: You are watching all bug changes.
