https://bugs.kde.org/show_bug.cgi?id=466126

Duncan <1i5t5.dun...@cox.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
                 CC|                            |1i5t5.dun...@cox.net
             Status|REPORTED                    |RESOLVED

--- Comment #2 from Duncan <1i5t5.dun...@cox.net> ---
This is almost certainly a duplicate of bug #351175.   Marking it as such. 
However, I'm just another user with another dupe, not a dev, so if you think
it's not a dupe, feel free to reverse that and explain the difference.

Briefly, the problem is with "internal" borders/edges (aka "struts") between
monitors.  As long as the panel is on a true edge of the bounding rectangle
things are fine, but put it on a strut that's "internal", not on the bounding
rectangle edge, and the autohide does the immediate re-popup thing exactly as
you describe.

Unfortunately fixing this bug doesn't appear to be a priority, despite the
number of dupes and thus users obviously affected.

Two known workarounds:

1) Change your layout and/or panel position to avoid placing panels on such
"internal" struts.

(This one's obvious once the problem is understood. For me, it was the excuse I
needed to upgrade my older FullHD monitor to a second 4K so they'd match sizes
and I'd have no need to place a panel on the previously partial seam between
them.)

2) It has been reported that separating the monitors in the kscreen layout so
they don't logically touch eliminates the issue as it fools the logic into
thinking all the edges are external, while still allowing the pointer to move
between screens (which I thought would be broken, but apparently not).

IMO that's quite clever and I really wish I had thought to try it before
throwing money at the problem (but of course that would have done away with my
excuse to upgrade =:^)

*** This bug has been marked as a duplicate of bug 351175 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to