Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WorkspaceCommandStack.isSaveNeeded() does not consider AbstractCommand.NonDirtying #30

Open
pcdavid opened this issue Sep 4, 2022 · 1 comment
Labels
bugzilla Issues migrated from the old Eclipse Bugzilla

Comments

@pcdavid
Copy link
Contributor

pcdavid commented Sep 4, 2022

  • πŸ†” Bugzilla ID: #551164
  • πŸ“˜ Project: Modeling / EMF Services / Transaction
  • πŸ—“ Created: 2019-09-17T12:25:16Z
  • ❓ Status: NEW /
@pcdavid pcdavid added the bugzilla Issues migrated from the old Eclipse Bugzilla label Sep 4, 2022
@pcdavid
Copy link
Contributor Author

pcdavid commented Sep 4, 2022

Comment #0 on Tue Sep 17 2019 14:25:16 GMT+0200 (Central European Summer Time):

According to Ed's proposal in https://www.eclipse.org/forums/index.php/m/1814570/#msg_1814570 I file this bug.


We are using TransactionalEditingDomain with a WorkspaceCommandStack.
org.eclipse.emf.edit.ui.action.CopyAction (or the used CopyCommand) makes the editor dirty.

In the editor a CommandStackListener is registered. When an event is raised, it tells the editor to check it's dirty property. The editor then calls WorkspaceCommandStack.isSaveNeeded(). Which always returns true, even for a copy command which does not change the editor's content.
In comparison the BasicCommandStack.isSaveNeeded() method asks the command whether it has changed the model.

Comment #1 on Tue Sep 17 2019 16:45:08 GMT+0200 (Central European Summer Time):

Marcus,

This isn't the most active project so if you really need a fix, you might consider contributing one or sponsoring someone.

Comment #2 on Sat May 14 2022 15:51:35 GMT+0200 (Central European Summer Time):

Eclipse EMF Transaction is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse/emf-transaction.

If this issue is relevant to you and still present in the latest release:

* Create a new issue at https://github.com/eclipse/emf-transaction/issues/.
  * Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience)
  * In the GitHub description, start with a link to this bugzilla ticket
  * Optionally add new content to the description if it can helps towards resolution
* Update bugzilla ticket
  * Add to "See also" property (up right column) the link to the newly created GitHub issue
  * Add a comment "Migrated to <link-to-newly-created-GitHub-issue>"
  * Set status as CLOSED MOVED

All issues that remain open will be automatically closed next week or so. Then the Bugzilla component for EMF Transaction will be archived and made read-only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugzilla Issues migrated from the old Eclipse Bugzilla
Projects
None yet
Development

No branches or pull requests

1 participant