| Summary: | canceled commands still mark editor dirty and appear in the command stack | ||
|---|---|---|---|
| Product: | [Modeling] Graphiti | Reporter: | Henrik Rentz-Reichert <hrr> |
| Component: | Core | Assignee: | Michael Wenz <michael.wenz> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ashw.kumar, dhawal.joshi, michael.wenz, tim.kaiser |
| Version: | 0.7.0 | Flags: | michael.wenz:
indigo+
|
| Target Milestone: | 0.8.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | Indigo M4 M7 theme_bug 0.7.2 | ||
|
Description
Henrik Rentz-Reichert
In this case a CommandContainer is processed in the command stack but only for FeatureCommands the check hasDoneChanges is performed. Inside the container are again FeatureCommands, so the unpackking of the container is missing. it seems that also public boolean hasDoneChanges() for a AbstractCreateFeature derived feature is not called This issue is fixed now. hasDoneChanges() is now called for all kinds of features executed on the Graphiti command stack. With Graphiti 0.8.0 hasDoneChanges() is still not called in the case of a double click feature. See also the proposal in bug 340627. ShapeEditPart.performRequest triggered the feature execution in a non-standard way. I have just changed that, so now double click features also can prevent marking the editor dirty. Reopened because of an Email request by CPL to downport this fix to the 0.7 codeline. Part of Graphiti Indigo 0.8.0 Reopened for the downport to 0.7 Prepared changes have been checked-in to 0.7 branch Graphiti 0.7.2 build containing the fix is available Graphiti service release 0.7.2 is released and availble for download |