The bug-fix in revision 16531 introduced another bug. This is the right fix. I did...

[lyx.git] / src / BufferView.C

diff --git a/src/BufferView.C b/src/BufferView.C
index bac8364e2b04ceb8cd107ed014304ec7ee69a1e2..927d1f1ad6a599911fed5c43c674dd1c91e1fd2b 100644 (file)
--- a/src/BufferView.C
+++ b/src/BufferView.C
@@ -1331,6 +1331,7 @@ ViewMetricsInfo const & BufferView::viewMetricsInfo()
 }
 
 
+// FIXME: We should split-up updateMetrics() for the singlepar case.
 void BufferView::updateMetrics(bool singlepar)
 {
        LyXText & buftext = buffer_->text();
@@ -1342,13 +1343,10 @@ void BufferView::updateMetrics(bool singlepar)
                offset_ref_ = 0;
        }
        
-       // In singlepar mode, the anchor has to be reset because
-       // there is no metrics update with keyboard mouvement or
-       // mouse clicking if this didn't resulted in scrolling.
-       // FIXME: We should splitup updateMetrics() for the singlepar
-       // case.
-       if (singlepar)
-               anchor_ref_ = cursor_.bottom().pit();
+       // If the paragraph metrics has changed, we can not
+       // use the singlepar optimisation.
+       if (singlepar && tm.redoParagraph(cursor_.bottom().pit()))
+                       singlepar = false;
 
        pit_type const pit = anchor_ref_;
        int pit1 = pit;