https://bugs.documentfoundation.org/show_bug.cgi?id=152073
Rafael Lima <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|graphics stack |UI Keywords| |needsDevAdvice --- Comment #2 from Rafael Lima <[email protected]> --- After taking a long look at the code I found out what the problem is... but fixing it might be a bit more complicated than I thought. The problem is with how WB_BORDER is dealt with in windows created using the kf5 backend. This bug report is affected by two such windows: 1) The "window" that has the line numbers: https://opengrok.libreoffice.org/xref/core/basctl/source/basicide/linenumberwindow.cxx?r=0d9231f2#20 2) The "window" containing the code editor https://opengrok.libreoffice.org/xref/core/basctl/source/basicide/baside2b.cxx?r=be6024a2#243 Note that both are created using the WB_BORDER flag so that a thin border is drawn around the window. The problem is that, for some reason, in kf5 the border is drawn with an additional "black" outer border line with 1 pixel in size. Then when the window is resized (f.i. when the line number window needs more width) and the Editor Window is moved to the right, the remnants of the previously drawn window that was below the black pixels stay there. They never get removed. To test this, simply remove the WB_BORDER flag and you'll notice that the problem disappears (as well as the borders...). This makes me wonder if the problem is a bit deeper and relates to how window borders are drawn in general. I would like to get some input from devs to see if my assessment is correct... and maybe point to some direction to provide a definitive fix for this issue. -- You are receiving this mail because: You are the assignee for the bug.
