Community

As per post here
http://forum.textpad.com/viewtopic.php? ... 849e718b25

Please provide an option that switches cursor behaviour so that up/down maintains CURRENT position and doesn't flip back to the column position at which you started typing on the line you're moving off.

<Post Script>
You can avoid this behaviour by creating a macro that moves left one, right one, up one, then assigning that macro to the Up-csr key. Obviously, sim for down.
</Post Script>

Why do you post this under Enhancement Suggestions?
Posting under Enhancement Suggestions implies that Textpad does not have that option.

Configure - Preferences - Editor
Un-check "Constrain Cursor to Text"

Because changing that option doesn't have the desired effect.

Ok, it does have the desired effect if I switch word-wrap off, but with word-wrap on it makes no obvious difference.

It seems to work OK for me with/without word wrap. Obviously on shorter lines, the cursor will shift left.

Since it works for us and not for you, then I wonder about your statement

CURRENT position and doesn't flip back to the column position at which you started typing on the line you're moving off.

What is the difference between where you are moving from, and the current position? This may be what is confusing to the solution.

Did you read the post in the other forum I referenced?

Open a window with the following 3 lines in them
Line 1
Line 2
Line 3

Place the cursor at the beggining of line 2 and overtype "Line" with "Type", press the up-cursor-key or the down-cursor-key and the cursor is at the start of line 1-or-3 instead of at position 5 where it was when I finished typing "Type" on line 2.

I would like to add that there are occasions this feature can be useful, and I would use it from time to time, but as a touch-typist, I watch the screen not the keyboard as I type, so my eyes are fixed on the cursor, then if I move it up/down after a hefty amount of typing, Bang! where's the flippin cursor gone?

As the person in the other forum said, "Constrain cursor to text"-> off has its own set of annoyances, and for me at least, word-wrapped files still suffer with the same grievance. (I use the word very lightly compared to the plight of people in the third world, war-stricken regions, the list is endless, but it just bugged me one too many times...)

Thanks for Line1,2,3 example. Now I see what you are talking about.

It appears that this "only" happens on the single line you have just edited, but is OK on all other lines. But I can see how that can be an issue. Never noticed it before.....now I will see it all the time ,,, aaargh!