https://bugs.kde.org/show_bug.cgi?id=351175
--- Comment #19 from Duncan <1i5t5.dun...@cox.net> --- (In reply to Sergio from comment #18) > Still an issue as of: > KDE Plasma Version: 5.18.5 > KDE Frameworks Version: 5.68.0 > Qt Version: 5.12.8 > > @David Edmunson, can you please clarify what limitation exists in X making > it impossible to have an autohiding panel on a screen edge that is also the > edge of another monitor? > > As a matter of fact, in my system when you hover on the panel, right after > it *does* autohide perfectly. The problem is that immediately an unhide is > triggered even if there is no reason for that. FWIW I worked around the bug here with hardware, getting a second TV/Monitor the same size and 4K resolution so I didn't have the half-border (I ran into the bug while running a 4K and a FHD monitor, with a layout triggering the bug on an internal-border panel that needed to be there due to the different sizes), which let me change the logical layout so I could put my panels on the external borders where the bug doesn't happen. But the bug's still irritating. I'm not a dev, but I do run gentoo so build from source, and have been running the live-git packages from the gentoo/kde overlay for probably the better part of a decade now. While I can't really do new code, during that time I've gotten reasonably good at at least hack-patching, particularly when I have a recent commit pointing me at the code I'm interested in. But I recently proved to myself that a recent commit pointing the way isn't always necessary (unrelated to this bug, Oxygen theme titlebar height actually, see bug #425874 if interested), I just have to find the current behavior even more irritating since it's more work to find the code in question. Of course then the code has to be clear, well organized, and commented enough for me to figure out even as a non-dev, but thankfully, kde/plasma code tends to be just that, clear, well organized and well commented, so at least sometimes it can be possible. And this bug is irritating! So no promises, but if it works out and I can find and at least hack-patch demonstrate that a fix is possible, perhaps the real devs will use that as a start to a real patch to fix it properly. But I gotta actually find the code in question and see if I can hack-patch it first. We'll see... -- You are receiving this mail because: You are watching all bug changes.
