proposed method of deleting statements- opinions solicited

I created an EditorAction that writes into a file. I want to provide the user the opportunity to unwrite those changes. I would like to treat those changes as first class objects, and not just Undoables on the undo stack.


What I implemented was a static member ArrayList that holds a reference to those PsiStatements. I could also create a Singleton with the same information.

At any rate, I propose referencing that ArrayList and removing / deleting (however THAT'S done - I know not yet ) each of its contained PsiStatements.


Why is this a bad idea that is going to blow up in my face? Or is it not a bad idea?

Message was edited by:
softwarevisualization

1 comment

Hello softwarevisualization,

I created an EditorAction that writes into a file. I want to provide
the user the opportunity to unwrite those changes. I would like to
treat those changes as first class objects, and not just Undoables on
the undo stack.

In other words, in most cases, the user will not want to undo
everything that happened after I wrote to their file, but rather just
undo what the EditorAction wrote to their file.

Is this possible?


You'll need to implement this manually. IDEA's undo actions work strictly
as a stack: you can't undo an action that isn't on the top of the stack.

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

Please sign in to leave a comment.