Version: (using KDE 4.3.4) Installed from: openSUSE RPMs this is a usability problem: when I want to close a window (aligned to right/top screen corner) with the mouse, I simply go to the screen edge and click. in kde4 the window decorations have no sensivity for the close-button in the corner (in kde3 and windows this works as expected). I don't know if this is a decoration-problem or a kwin problem or ??? same for the taskbar items in the panel which I want to activate. the panel is always on an edge of the screen, and as I can see, they are sensitive on top of their visible area, but not below. same for kmenu/kickoff.
another perhaps related thing: I can move the mouse to the right screen border, so that the mouse-pointer is not visible anymore. this makes no sense. at least 1 pixel should be visible. on bottom this is correct: there is one pixel visible always.
Please file bugs individually. 1. Close button region in window decorations not extending to the screen edges This only works with maximized windows, and the option "Allow to move maximized windows" off (default). It also depends on the used decoration. With Skulpture, for example, this works as expected. You could check which decorations work, and file bug reports for the decorations where this does not work. Use bugzilla product "Oxygen" for the Oxygen window decoration. 2. Taskbar item region in panel not extending to the screen edges This probably also depends on the used theme (Plasma theme in this case). Here, with theme Atelier with a panel on the top, the mouse can be moved to the extreme top to activate the taskbar items. I think Plasma panel should make sure this works with any theme, so I am reassigning this bug to the Plasma team. 3. Kickoff icon click region not extending to the screen edges Again, cannot reproduce here. See above. 4. Mouse cursor pixels not visible at particular screen edges The "hot spot" of the mouse cursor is specified in the used cursor theme. I use a cursor where exactly the opposite effect is visible: When I move the cursor to the bottom, no pixel is visible :) Depending on which theme you use, please file a bug report to Oxygen or freedesktop.org in case of X11 cursor themes.
1.+ 4.: I tested all available window decorations now (incl. Skulpture). And all available mouse-pointer-designs. And ALL had the same problem, that at the right border (where the mouse button is out of the screen), the close button is not sensitive. I don't have the impression, that this is a style problem. Especially because skulpture works for you and not for me. 4.: the mouse pointer behaves exactly the same for all cursor-themes. So it would be good, to find out, what is the reason, why it does not work for me. I have no idea. It is a standard opensuse-11.2 with kde-4.3.4 installation (from kde43 repository), with qt-4.6 from kde4-unstable-repository.
I now tested a little more: the problem does not exist in gnome with same hardware/monitor-settings, even with kwin-4 enabled. The mouse pointer is also always visible in gnome.
I don't know what I have done, but it works now: mouse pointer is visible allways and so hover is always triggered. Perhaps I leave this bug a while open, I hope that I will find the reason for this.
now I know, when the mouse pointer is affected: If I switch off my LDVS (internal notebook screen) and only use my external DVI LCD display. The external display works as expected, when both screens are enabled. by the way: I have to turn the LDVS off every session because kde does not remember that.
Hello! This feature request was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this feature request is already implemented in Plasma 5, or is no longer applicable. Accordingly, we hope you understand why we must close this feature request. If the requested feature is still desired but not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham