The following patch fixes several bugs with insettabular/insettext (mostly RTL
stuff). I've also made one change which isn't exactly a bug fix:
When you press tab in a tabular cell, and the cursor is in a non-dummy position
(i.e. the red frame is displayed, or technically, the insettext of the current
cell is locked) the cursor will move into a non-dummy position in the next
cell.
I think that this makes the insettabular a little bit less confusing to the
user. This idea can be taken further:
1. When you enter a table with the cursor/create a new table, the cursor will
be in a non-dummy position.
2. If the cursor is in a non-dummy position, then pressing an arrow key will
move the cursor into a non-dummy position (either in the same cell or in a
different cell).
The above is a small change, so should it be done for 1.1.6 ?
Question to Juergen:
1. Please check InsetText::checkAndActivateInset and
InsetTabular::ActivateCellInset. I think that the old code was wrong
(namely decreasing inset_x/inset_y from x/y) but I'm not sure.
2. Why the insettabular needs two "dummy" cursor positions per cell ?
patch.gz
