global limit on undo/redo stack [message #508871] |
Wed, 20 January 2010 15:36 |
|
Hi,
I want to set a global limit on undo/redo stack (as it is a EMF/GMF Operation it is huge...)
I already set limit on each IUndoContext of editor but when we have a lot of opened editor it can be too much.
How can I set a global limit?
Regards,
Aurelien
Aurélien Pupier - Red Hat
Senior Software Engineer in Fuse Tooling team
|
|
|
|
[SOLVED]Re: global limit on undo/redo stack [message #508895 is a reply to message #508871] |
Wed, 20 January 2010 16:16 |
|
thanks for your quick reply.
Effectively, reading more carefully some comment in the implementation of DefaultOperationHistory.setLimit :
/*
* The limit checking methods interpret a null context as a global limit
* to be enforced. We do not wish to support a global limit in this
* implementation, so we throw an exception for a null context. The rest
* of the implementation can handle a null context, so subclasses can
* override this if a global limit is desired.
*/
Assert.isNotNull(context);
So as it is not possible there is the issue describe in my other post. (free the OperationHistory on editor closed)
Aurélien Pupier - Red Hat
Senior Software Engineer in Fuse Tooling team
|
|
|
Powered by
FUDForum. Page generated in 0.03780 seconds