summaryrefslogtreecommitdiff
path: root/chart2/source/model/main
diff options
context:
space:
mode:
authorFrank Schoenheit [fs] <frank.schoenheit@oracle.com>2010-11-16 15:38:33 +0100
committerFrank Schoenheit [fs] <frank.schoenheit@oracle.com>2010-11-16 15:38:33 +0100
commitec5f9c18235b50d564da5e23d99d4844667db5b1 (patch)
tree37238fc3e9d46a7403abc0a6747ed2ac0d452904 /chart2/source/model/main
parent247ba6c56c0bf4e27744b2b895411247420bebcf (diff)
undoapi: respect the config limiting the maximum number of undo actions. No life-update anymore, i.e. changes in this setting are respected by new instances only, not by existing instances. This is a degradation (a bearable, IMO) compared to the old implementation, but consistent with other apps. So, why adding unnecessary complexity?
Diffstat (limited to 'chart2/source/model/main')
-rwxr-xr-xchart2/source/model/main/UndoManager.cxx2
1 files changed, 2 insertions, 0 deletions
diff --git a/chart2/source/model/main/UndoManager.cxx b/chart2/source/model/main/UndoManager.cxx
index b88f40307d8a..8e9ee25fa0c5 100755
--- a/chart2/source/model/main/UndoManager.cxx
+++ b/chart2/source/model/main/UndoManager.cxx
@@ -35,6 +35,7 @@
#include <framework/undomanagerhelper.hxx>
#include <svl/undo.hxx>
+#include <unotools/undoopt.hxx>
//......................................................................................................................
namespace chart
@@ -84,6 +85,7 @@ namespace chart
,m_aUndoManager()
,m_aUndoHelper( *this )
{
+ m_aUndoManager.SetMaxUndoActionCount( (USHORT)SvtUndoOptions().GetUndoCount() );
}
virtual ~UndoManager_Impl()