Community
Participate
Working Groups
Build Identifier: 20110301-1815 / 0.9.0.v20110818-1338 The pattern implementations use the class DeleteFeatureForPattern that extends DefaultDeleteFeature and therefore contain its own property doneChanges. Following the attribute chain delegate --> pattern --> wrappedDeleteFeature, there's a different instance of DefaultDeleteFeature that handles the actual object deletion and sets its own attribute doneChanges to true. The command stack performs a check to see whether any changes were made, and as far as I can see, it only checks the "outer" DeleteFeatureForPattern instance. The doneChanges attribute of this class is never set to true, so the entire undo stack is reverted. I'll attach a screenshot to illustrate the problem. Reproducible: Always
Created attachment 202330 [details] screenshot of debugger
After enabling delete in our SDDT sample this id reproducable
Fixed. The "outer" feature delegates the call hasDonechanges() to the "inner" feature/pattern.
Bookkeeping: Set target release
Part of Graphiti 0.9.0 (Eclipse Juno)