| commit | 6ad096aeeb5c85a82fba70526569f074b67a083c | |
| author | Ashod Nakashian <ashod.nakashian@collabora.co.uk> | |
| Tue, 2 Oct 2018 09:20:38 +0000 (2 05:20 -0400) | ||
| committer | Ashod Nakashian <ashnakash@gmail.com> | |
| Mon, 3 Dec 2018 07:12:23 +0000 (3 08:12 +0100) | ||
| tree | 47b071d5297e5110f1498d4d75608e8ae2aff18c | treesnapshot (tar.gz zip) |
| parent | 3750d0533e0e00941e5aef92fe5a26b6e7e27734 | commitdiff |
sw: paragraph-sign: validate current SwTextNode directly
When invoking undo, it turns out that the cursor position
is updated after the text modification, which triggers the
paragraph signature validation. Relying on the cursor
position, then, results in the wrong (previous) paragraph
to be validated (if the undo is in a different paragraph).
Since we have the correct SwTextNode when it's modified
(due to undo or otherwise), there is no reason why
we shouldn't use it and try to deduce it from the cursor.
Change-Id: I4c3283d59738988dcc1c592a9f3ef2c818ce675d
Reviewed-on: https://gerrit.libreoffice.org/63004
Tested-by: Jenkins
Reviewed-by: Ashod Nakashian <ashnakash@gmail.com>
When invoking undo, it turns out that the cursor position
is updated after the text modification, which triggers the
paragraph signature validation. Relying on the cursor
position, then, results in the wrong (previous) paragraph
to be validated (if the undo is in a different paragraph).
Since we have the correct SwTextNode when it's modified
(due to undo or otherwise), there is no reason why
we shouldn't use it and try to deduce it from the cursor.
Change-Id: I4c3283d59738988dcc1c592a9f3ef2c818ce675d
Reviewed-on: https://gerrit.libreoffice.org/63004
Tested-by: Jenkins
Reviewed-by: Ashod Nakashian <ashnakash@gmail.com>
| sw/inc/editsh.hxx | diffblobblamehistory | |
| sw/source/core/edit/edfcol.cxx | diffblobblamehistory | |
| sw/source/core/txtnode/ndtxt.cxx | diffblobblamehistory |