[#IDEADEV-5520] Option to not scroll editor (unless required)

IDEA: Development

Option to not scroll editor (unless required)

Created: 13 Feb 06 14:45 Updated: 27 Dec 06 21:47

Component/s:

Editor. Editing Text

Fix Version/s:

Demetra 5231

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

Build:	5,131
Fixed in build:	5,222
Severity:	Medium

Description

« Hide

I always feel uneasy when Idea scrolls the editor to center the caret row vertically (e.g. when navigating to the next find result, or when a breakpoint is hit).
As long as the new caret row is already visible and more than N rows away from the lower or upper editor margin, Idea should not scroll at all.
It always leaves me disoriented for a fraction of a second (and smooth scrolling does not help at all, but makes me kind of seasick).
This should probably be an option:

After changing caret row:
O Center new row
O Don't scroll if new row is at least ____ rows away from the margin

(Or maybe "Scroll only so that new row is _____ rows away of the margin"?)
Even if scrolling needs to be done because the caret row is currently invisible or is within the margin area, it should be kept minimal, i.e. scroll only so many rows as needed to make the row appear outside of the margin.

Note that the current behaviour is absolutely non-standard, so there should be very good reasons to stick with it.
Apparently I am not the only one wanting the standard behaviour:
http://www.intellij.net/forums/thread.jsp?forum=22&thread=196007

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Chris Miller - 13 Feb 06 16:23

I think it's a bit fine-grained to be worth having an option for, just sensible behaviour along the same lines as almost every other text editor out there would suffice.

[ Permlink | « Hide ]

Stephen Friedrich - 13 Feb 06 18:21

Me, myself and I could live without the option as well. It's just that I faintly remember a discussion some years ago where somebody from jetbrains strongly argued for the current behaviour.
(IIRC the 'smooth scrolling' option was added as a result of that discussion. But for me it feels even worse.)

[ Permlink | « Hide ]

Keith Lea - 13 Feb 06 19:02

I don't want an option either, I just want it to stop scrolling when it doesn't need to.

[ Permlink | « Hide ]

Maxim Shafirov - 09 Apr 06 22:20

Well, there will be an option. People usually are very sensitive when such a basic behavior things do change.
It sounds like:
O Prefer scrolling editor canvas to keep caret line centered
O Prefer moving caret line to minimize editor scrolling

[ Permlink | « Hide ]

Stephen Friedrich - 09 Apr 06 22:45

Wow. I had given up hope

How about making the new behaviour the default for the next EAP build
and just wait and see what people say about it?
Otherwise it may go unnoticed by many who would maybe appreciate the
change.

OTOH you're right of course, people are sensitive about this, but EAP is
mostly for gathering feedback, so IMHO you should take your chances.
If you're right and most people prefer the old behaviour you can just as
well switch back to the old behaviour in a later EAP build...

[ Permlink | « Hide ]

Jon Steelman - 09 Apr 06 22:49

> Well, there will be an option.

Thank goodness for no more seasickness when searching! I had never become accustomed to the present behavior and looking forward to trying it out.

Much appreciated,
Jon

[ Permlink | « Hide ]

Maxim Shafirov - 09 Apr 06 22:55

Hello Stephen,

I'll see how it goes myself first, OK? Or my coworkers gonna kill me even
before this build is publically available

------------------
Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

[ Permlink | « Hide ]

Maxim Shafirov - 27 Dec 06 21:47

Hello Stephen,

I'll see how it goes myself first, OK? Or my coworkers gonna kill me even
before this build is publically available

------------------
Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

[ Permlink | « Hide ]

NNTP User - 27 Dec 06 21:47

Wow. I had given up hope

How about making the new behaviour the default for the next EAP build
and just wait and see what people say about it?
Otherwise it may go unnoticed by many who would maybe appreciate the
change.