Add SCI_GETUNDOSEQUENCE to determine whether an undo sequence is active and its

nesting depth.

1 files changed, 19 insertions, 0 deletions

diff --git a/test/simpleTests.py b/test/simpleTests.py
index 1ca5b76cb..ce67edfde 100644
--- a/test/simpleTests.py
+++ b/test/simpleTests.py
@@ -221,6 +221,25 @@ class TestSimple(unittest.TestCase):
 		self.assertEqual(self.ed.CanRedo(), 0)
 		self.assertEqual(self.ed.CanUndo(), 1)
 
+	def testUndoSequence(self):
+		data = b"xy"
+		self.assertEqual(self.ed.UndoSequence, 0)
+		self.ed.InsertText(0, data)
+		self.assertEqual(self.ed.UndoSequence, 0)
+		# Check that actions between BeginUndoAction and EndUndoAction are undone together
+		self.ed.BeginUndoAction()
+		self.assertEqual(self.ed.UndoSequence, 1)
+		self.ed.InsertText(0, data)
+		self.ed.InsertText(1, data)
+		# xxyyxy
+		self.assertEqual(self.ed.Length, 6)
+		self.ed.EndUndoAction()
+		self.assertEqual(self.ed.UndoSequence, 0)
+		self.ed.Undo()
+		# xy as 2 inserts removed
+		self.assertEqual(self.ed.Length, 2)
+		self.assertEqual(self.ed.UndoSequence, 0)
+
 	def testUndoSavePoint(self):
 		data = b"xy"
 		self.assertEqual(self.ed.Modify, 0)