This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 16016 - Cursor should follow scrolling to always be on screen (optionally)
Summary: Cursor should follow scrolling to always be on screen (optionally)
Status: RESOLVED DUPLICATE of bug 105494
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Windows 3.1/NT
: P3 blocker with 2 votes (vote)
Assignee: issues@editor
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-09-28 06:38 UTC by K.C. Baltz
Modified: 2009-01-03 12:55 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description K.C. Baltz 2001-09-28 06:38:21 UTC 
Currently, if the screen is scrolled using CTRL-Up/Down or the mousewheel, the 
cursor position is left unchanged.  Thus, when a key is pressed, the view is 
immediately returned to where the cursor can be seen.  I'm proposing that, if a 
given option is invoked, the cursor should always be visible, being "pulled" 
along as the screen is scrolled.  If the screen is scrolled down, at the point 
the cursor would leave the screen, it should move down a row so as to remain on 
screen.  Same logic for scrolling up.
Comment 1 Jan Chalupa 2001-11-27 12:27:09 UTC 
Target milestone -> 3.3.1.
Comment 2 Marek Grummich 2002-07-22 10:09:30 UTC 
Set target milestone to TBD
Comment 3 brenthale 2003-02-11 16:59:32 UTC 
Another alternative way of implementing this would be to 
preserve the cursor on the same logical row as you perform 
the CTRL-UP/Down.  I don't mind the way proposed above 
either (its better than the way it currently is).  But (in 
the case of scrolling down) I usually like to have several 
lines below me while editing.  Implementing it so that the 
cursor has to go all the way to the bottom would require 
me to scroll down to where I want the bottom of the text 
and then press Up several times to get back to the editing 
spot.  If the Ctrl-Up/Down locked the logical row, I could 
scroll precisely to where I wanted to edit and still see 
the text below or above without the extra keystrokes.
Comment 4 Petr Dvorak 2009-01-03 12:55:38 UTC 
Making as a duplicate of newer issue. Please reassign your votes...

*** This issue has been marked as a duplicate of 105494 ***