Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » global limit on undo/redo stack
global limit on undo/redo stack [message #508871] Wed, 20 January 2010 15:36 Go to next message
Aurélien Pupier is currently offline Aurélien PupierFriend
Messages: 637
Registered: July 2009
Location: Grenoble, FRANCE
Senior Member

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
Re: global limit on undo/redo stack [message #508883 is a reply to message #508871] Wed, 20 January 2010 16:01 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 33137
Registered: July 2009
Senior Member
Aurelien,

There isn't such a global limit.


Aurelien Pupier wrote:
> 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
>
>


Ed Merks
Professional Support: https://www.macromodeling.com/
[SOLVED]Re: global limit on undo/redo stack [message #508895 is a reply to message #508871] Wed, 20 January 2010 16:16 Go to previous message
Aurélien Pupier is currently offline Aurélien PupierFriend
Messages: 637
Registered: July 2009
Location: Grenoble, FRANCE
Senior Member

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
Previous Topic:OperationHistory not cleaned after editor closed
Next Topic:Eclipse launcher & max heap size problem
Goto Forum:
  


Current Time: Fri Apr 19 23:35:32 GMT 2024

Powered by FUDForum. Page generated in 0.03211 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top