Bug 56280 - mouse scroll wheel movement to large
Summary: mouse scroll wheel movement to large
Status: CLOSED FIXED
Alias: None
Product: calligraflow
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Peter Simonsson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-23 18:00 UTC by Ferdinand Gassauer
Modified: 2003-04-04 17:29 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ferdinand Gassauer 2003-03-23 18:00:35 UTC
Version:           1.2post (using KDE 3.1.9)
Compiler:          gcc version 3.2 (SuSE Linux)
OS:          Linux (i686) release 2.4.19-4GB

Hi!
scrolling a kivio page up and down moves immediately to the top/bottom part of the page. 
IMHO it should scroll  in much smaller steps through the pages.
cu
ferdinand
Comment 1 Peter Simonsson 2003-04-01 19:51:58 UTC
Currently the wheel scrolls the height of the visible area. What would you say is a more 
acceptable length to scroll? 
Comment 2 Ferdinand Gassauer 2003-04-02 05:43:42 UTC
Subject: Re:  mouse scroll wheel movement  to large

On Tuesday 01 April 2003 19:52, you wrote:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=56280
> psn@linux.se changed:
>
>            What    |Removed                     |Added
> ---------------------------------------------------------------------------
>- AssignedTo|kivio-devel@thekompany.com  |psn@linux.se
>
>
>
> ------- Additional Comments From psn@linux.se  2003-04-01 19:51 -------
> Currently the wheel scrolls the height of the visible area. What would you
> say is a more acceptable length to scroll?
kword scrolls in 10 steps (4 lines / step) through one visible page 
also kmail scrolls 3-4 lines per step

BTW the scrolling sems to be  independent of the resolution (zoom level)

hope that helps

Comment 3 Peter Simonsson 2003-04-04 17:28:43 UTC
*** Bug has been marked as fixed ***.