Bug 108374 - Newly inserted first line not scrolled to
Summary: Newly inserted first line not scrolled to
Status: RESOLVED FIXED
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: 2.4
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-30 19:24 UTC by Gluon
Modified: 2007-12-13 19:47 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Gluon 2005-06-30 19:24:33 UTC 
Version:           2.4 (using KDE KDE 3.4.0)
Installed from:    Unspecified
OS:                Linux

Current behaviour:
When the text-cursor is at the beginning of of the first visible line in the scroll area and i want to insert a new line by pressing enter, the new line is being inserted correctly, but the vertical scrolling position of the text area is not updated and the newly inserted line is not visible as the new first line.

Expected behaviour:
In my opinion the scroll-area should scroll up by one line after pressing enter to show the new line above. Otherwise someone (like me) could possibly not recognize the successfull insertion...
Comment 1 Christoph Cullmann 2005-09-28 23:06:09 UTC 
Fixed for KDE 3.4.1 and upwards, yeah, was bad >= typo in code ;)
Comment 2 Mihai Basa 2007-06-29 17:00:05 UTC 
I believe this bug is active again for Kate 2.5.7 (KDE 3.5.7).

Pressing enter at the beginning of a document does not move existing text down, but inserts new lines above the cursor, and outside the visible screen. The impression for the user is that nothing is happening when they press enter.

Can this bug be re-opened?
Comment 3 Akarsh Simha 2007-12-10 20:23:16 UTC 
It seems like this bug still persists in the current SVN snapshot of Kate.

Can this be reopened?
Comment 4 Thomas Friedrichsmeier 2007-12-13 19:47:42 UTC 
Which sort of SVN snapshot do you use (KDE 3.5 or KDE 4)? I can reproduce in KDE 3.5.8, but not KDE 4. BTW, bug #146300 is still open about this same issue (but only for another while), if you can still reproduce in KDE 4, I suggest adding a comment there, as well.