Abdelrazak Younes schrieb:
Dov Feldstern wrote:
Bernhard Roider wrote:
As i said this is a more general issue: when the cursor is positioned
at the end of the first (last) line in an inset then the up (down)
arrows do not what they are expected to: move out of the inset.
An investigation in case of the tabular inset showed that if the text
dispatch handles the cursor movement (changes the cursor) then it
does nothing by itself. The attached patch fixes that, but i don't
know why the removed condition is in there - maybe it has another
reason. I think it's from changeset 16638.
Bernhard
I did a little detective work, and haven't come up with much, but it
all points to Abdel ;) , so you'd better ask him:
Check out this thread
http://permalink.gmane.org/gmane.editors.lyx.devel/75646, which
discusses the changeset that you mentioned. In that thread, Abdel says
that it us something he had removed a few days before --- I tracked
that down to changeset 16433.
You are right Dov.
I don't know why it was put back with that condition, though...
The idea is that when the cursor is at the end of a text line, if the
next (or previous) line is shorter you don't want to remember that
position because the cursor will jump two lines below instead where the
x-target is met. At least that was the case and the navigation used to
work fine with this condition. But maybe some code dealing with cursor
movement has changed since then, dunno. Please experiment before
committing Bernhard.
Was the intention that when there is a long line followed by a short line, followed by a long line
and you press down twice, starting torwards the end of the first long line, then you wanted to the
cursor to be torwards the end of the second long line?
eg. start at s, press down twice, land at e (instead of x)
0000000000000000000000000000000000000000s000
1111111111111111111111111111
2222222222222222222222222222x22222222222e2222
Bernhard
