scrolling a table with the sliders at right for up/down or bottom for left/right
creates artifacts, especially on FAST MOVEMENT
which resolves (!)/ disapear, if the mouse button (after slider movements) is released
I am not sure, if it relates to "viewing".
Win 7 / x64
Graphics-driver AMD Radeon legacy (HD 2400)
kind regards to all LO developers and all others
Created attachment 91201 [details]
part of screenshot
I just took part of a sreen, without table contend.
The artifacts are created by duplikated column / row numbers.
In real cells and their contend ar "dubbled / manyfolted" the same way.
Thanks for the screenshot Karl. Guess we'll have to wait for some windows users to confirm this glitch. I cannot reproduce this on OSX.
Created attachment 91275 [details]
creenshot 2 / duplicated cells
sorry, the lower part might be too small
upper is the cells in normal view,
below if thei are crolled by slider fast.
the cells are "duplicated" too.
originally the rightest cell is column "P"
then "duplicated up to coulumn "Y"
PS: the duplication "solves" if mouse button on slider is released
I don't reproduce using LO 188.8.131.52 & Windows 7 Home Premium.
Can you verify In Tools > Options > LibreOffice > View in Graphics Output
that Use hardware acceleration is checked?
I have a similar problem but so far no one can reproduce it.
Look at the bug 72401: https://bugs.freedesktop.org/show_bug.cgi?id=72401
Hardware Accell IS CHECKED,
but unchecking it doesnt change anything.
The lifetime of the artifacts is "until mouse button is released"
I can reproduce this bug running 184.108.40.206 on Windows 7
I can't reproduce this bug on mac
here is a video to show that happens: http://youtu.be/vf00Nxuq41s
(sorry for the bad quality)
The same on LO 220.127.116.11 (RC2)
MAY BE SOLVED !!!
I installed LO 18.104.22.168 today
and "srolled fast" through my tables.
I might say: I can't see the effects anymore.
Set to resolved works for me as the used said but found a dubplicate in the RC3 release note. so setting it as a duplicate
*** This bug has been marked as a duplicate of bug 68961 ***