Summary: | Local history improvement | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Xavier Méhaut <xmehaut> |
Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | ||
Version: | 2.0.2 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Xavier Méhaut
2002-10-01 05:31:02 EDT
Local history storage is provided by Core, moving report. As long as the changes are made with Eclipse editors, the appropriate Core API calls are made and then the changes are stored in the local history. If the changes are made via external editors (like Word and Excel) then the changes are discovered at the next refresh, at which time it is too late to put the old file contents into the local history. See also the following duplicate bug reports: bug 10589 bug 23091 *** This bug has been marked as a duplicate of 10589 *** it could be nevertheless interesting for this kind of document not to store inside changes but at least the whole document to be able to reload an old one... |