Bug 160981

Summary: kwrite doesn't scrool the text from side bar
Product: [Applications] kate Reporter: Cristi <cuciferus>
Component: kwriteAssignee: KWrite Developers <kwrite-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: andresbajotierra
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Cristi 2008-04-18 16:49:21 UTC
Version:           4.00.69 (KDE 4.0.69 >= 20080410) (using 4.00.69 (KDE 4.0.69 >= 20080410), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.24-gentoo-r3

Although scrooling the wheel above the text works the side bar from kwrite doesn't scrool the text, making it useless
Comment 1 Dario Andres 2008-08-01 02:52:44 UTC
Using KDE 4.1.00 (KDE 4.1.0) (KDEmod) in ArchLinux i686:
I can't reproduce this bug. I can scroll the text using the wheel in my mouse, the scrollbar or the Arrow keys.

What do you mean by "side bar" ? the scrollbar or another thing?

Can you reproduce this bug in the KDE4.1 release ?
Comment 2 Cristi 2008-08-01 07:31:14 UTC
Well...using kde 4.2.0 svn I am able to reproduce it. Here is how:
you open a text file or just punch some "new line"s in and then with the cursor over(above, don't know the excat term here) the scrollbar youu scroll the mose whell. Scrolling the wheel over the text does scroll the document.
Comment 3 Dario Andres 2008-08-01 13:45:39 UTC
Now I understand :) 

Using KDE 4.1.00 (KDE 4.1.0) (KDEmod) in ArchLinux i686: 
I can reproduce this bug.

Scrolling with the wheel ON the scrollbar will only move the scrollbar (the main content is fixed)

--

I can scroll the text using the wheel in my mouse (on the main content), moving the scrollbar (drag and drop, and arrows) or the Arrow keys.

Comment 4 Cristi 2008-08-01 14:13:43 UTC
funny right?
Comment 5 Dario Andres 2008-08-01 22:43:26 UTC
This is a duplicate of the (older) bug 158466
Comment 6 Cristi 2008-08-26 14:37:58 UTC
so it's not unconfirmed then

*** This bug has been marked as a duplicate of bug 158466 ***