Hello Jean-Marc, > I think I know why this happens: have a look at this comment taken from > coordCache.h: > > /** > * A BufferView dependent cache that allows us to come from an inset in > * a document to a position point and dimension on the screen.
> * The individual points are added at drawing time in > * BufferView::updateMetrics(). The math inset position are cached in > * the diverse InsetMathXXX::draw() calls and the in-text inset position > * are cached in RowPainter::paintInset(). > * FIXME: For mathed, it would be nice if the insets did not saves their > * position themselves. That should be the duty of the containing math > * array. > */ > But once we know that the row has to be slid, we could maybe draw it a > first time (it is possible to draw without actually drawing) to get > positions, and then do it a second time. Or we need to find what is the > place where this update happens. I tried drawing twice, but that did not overwrite the line. What I ended up with was, duplication content of the same line, where I cannot go through the duplicated content using arrow keys. Also I could not get an output which fixes the current wrong sliding. I see that I am really out of the schedule. But I feel like, it is worthless to try moving the next stage, without completing the first half correctly. And if I get succeed in fixing these, it would be easier to implement the next step. Thank you Hashini
