Community
Participate
Working Groups
Build Identifier: The editor keeps dirty when saving in push transaction. It's a bit confusing from the user experience, the editor should be clean after a commit in push transaction. Reproducible: Always
Created attachment 155083 [details] Patch v1 Please check if this suits your needs.
Created attachment 155091 [details] Patch v2 Added Strted and Finished events to push TX.
Committed to HEAD
There are two cases for which the editor appears to be dirty while it shouldn't: - After re-importing local changes - After pushing modifications in the repository I will provide a patch to fix this
Created attachment 155106 [details] Fix for the dirty state update after importing changes and pushing diffs in repo
Comment on attachment 155106 [details] Fix for the dirty state update after importing changes and pushing diffs in repo I confirm that I'm the only author and I apply the EPL.
Created attachment 155149 [details] Dirty state fix v2 I think your new code in the constructor was not very understandeable. Was your intent to set the dirty state of the push TX to the dirty state of the delegate TX before importChanges()? I guess my initial code did not consider that importChanges() causes CDOTransactionHandler events that, in turn, set the push TX to dirty. Wouldn't it be easier to just set the push TX dirty state to the delegate's initial dirty state after calling importChanges()? Please review my easier patch and tell me if it's still correct.
(In reply to comment #7) > Created an attachment (id=155149) [details] > Dirty state fix v2 > > I think your new code in the constructor was not very understandeable. Was your > intent to set the dirty state of the push TX to the dirty state of the delegate > TX before importChanges()? I guess my initial code did not consider that > importChanges() causes CDOTransactionHandler events that, in turn, set the push > TX to dirty. > > Wouldn't it be easier to just set the push TX dirty state to the delegate's > initial dirty state after calling importChanges()? Please review my easier > patch and tell me if it's still correct. Your modifications are ok for me.
Available in 3.0 GA: http://download.eclipse.org/modeling/emf/cdo/updates/3.0-releases/