https://bugs.documentfoundation.org/show_bug.cgi?id=149618

            Bug ID: 149618
           Summary: LibreOffice Calc - Brutal scrolling for large lines
           Product: LibreOffice
           Version: 7.2.4.1 release
          Hardware: All
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: medium
         Component: Calc
          Assignee: [email protected]
          Reporter: [email protected]

Description:
On Windows 10 (didn't try on the others OS), if I have big lines, when I scroll
down with the mouse wheel, instead of having a soft scrolling, which is what
I'd expect to work comfily on my files, it jumps off 3 lines, which is
extremely unpleasant and disorienting.

Someone on Internet made me noticed it's not the fault of the software, but the
fault of the Mouse Parameters on Windows 10. And indeed, I noticed that I can
change the numbers of lines it jumped off.
- But 1st, it changes the scrolling of all the other softawres (like Firefox or
LibreOffice Writer) definitely too slow
- And 2nd, it doesn't change the fact that if we have a big line, once we jump
off it, the scrolling is still too brutal, disorienting, and unpleasant.

Would it be possible to fix that and to suggest a scrolling which doesn't use
the Mouse Parameter of Microsoft Windows, so we can't jump off like that,
please?
This is really something necessary for me... and probably for the others who
use big lines on LibreOffice Calc.

Thank you.

Steps to Reproduce:
1. Making big lines on LibreOffice Calc (like 300 pts high)
2. Scrolling with the mouse wheel

Actual Results:
Getting disoriented, with a really unpleasant feeling

Expected Results:
Getting a soft scrolling, allowing us to stop feeling lost.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
None, except that from all the features I may find to request, this one is by
far the only and most essential for me.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to