Created attachment 137542 [details] Screenshot When OpenGL is enabled, the thickness of the selection rectangle depends on the cell position. See the attached screenshot. Likely Windows-only. Repro with LO 6.0 master build (d8f0e4144d51ff5709d005d289d71aa32f323913), 5.3.0.3 / Windows 7. Not reproduced with LO 5.2.0.4. => regression Early 5.3 builds with OpenGL enabled are very shaky on my system, all I can say it's in the first ~1k commits of 5.3 based on bibisect-win32-5.3.
No repro Version: 6.0.0.0.alpha1+ Build ID: b3f1d199a72ce87cb65ddaeac922564f57da6a4d CPU threads: 4; OS: Windows 6.3; UI render: GL; TinderBox: Win-x86@42, Branch:master, Time: 2017-11-06_00:10:53 Locale: nl-NL (nl_NL); Calc: CL
To be more precise, it depends on vertical position. If I start from row 1 and move down, it alternates between top and bottom being thick, somewhat thinner and thin, sometimes they match (eg. thin - thin), but not always. Ok, this might be GPU-dependent, I just tried with an Intel Ivy Bridge-series IGP (3xxx series CPU), and the thickness was even there (had to force OpenGL, though). The system where it happens has an AMD RX 570.
My bad, I can reproduce this Version: 6.0.0.0.alpha1+ Build ID: b3f1d199a72ce87cb65ddaeac922564f57da6a4d CPU threads: 4; OS: Windows 6.3; UI render: GL; TinderBox: Win-x86@42, Branch:master, Time: 2017-11-06_00:10:53 Locale: nl-NL (nl_NL); Calc: CL
Is this zoom-level depended?
(In reply to Telesto from comment #4) > Is this zoom-level depended? Yes, it shows different thickness for the same cell when I zoom in/out.
Created attachment 137574 [details] Bibisect log Regression introduced by: author Tomaž Vajngerl <tomaz.vajngerl@collabora.co.uk> 2016-05-29 06:36:39 (GMT) committer Tomaž Vajngerl <tomaz.vajngerl@collabora.co.uk> 2016-06-08 02:39:22 (GMT) commit 2003076c4318511a3d621558d3b44b4e8e6c6529 (patch) tree ecc2742bb911d2960ecd96f320a802ff8d43816f parent 344dc6939c45552dc162ea8b3f892e2ae4998d64 (diff) opengl: batch draw polypolygons
Thanks for the bibisect! Let's CC Tomaz Vajngerl.
Adding Cc: to Tomaž Vajngerl
Does this still happen? I ask as bug 107966 was bisected to this commit as well, and that was fixed last month. I can't reproduce this problem on Windows with my intel and nvidia cards, though -- even if I revert the fix.
Interestingly I can't repro it with a current master build, or even with the same state as the original repro. I wonder if the GPU driver got changed... anyway, let's close as WFM.