| Summary: | [Command] Make the CommandStack fields protected | ||
|---|---|---|---|
| Product: | [Tools] GEF | Reporter: | Pratik Shah <ppshah> |
| Component: | GEF-Legacy GEF (MVC) | Assignee: | gef-inbox <gef-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ahunter.eclipse, hudsonr, nyssen |
| Version: | 3.4 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Pratik Shah
One reason to not expose the field is to allow a CommandStack subclass to delegate to the IOperationHistory, in which case the private fields aren't even used. Maybe we could provide API that parallels the IOperationHistory API, like Command[] getUndoHistory(). Do you have a case where you continue appending an executed command right after save has occurred? This wouldn't be consistent with Office. The user should always be able to undo/redo to the saved state, rather than skipping past it. Exposing the field would - as Randy has already |