| Lost significant code edits while trying to refactor some class names [message #1718878] |
Thu, 31 December 2015 09:13 |
Eclipse User |
|
|
|
I just lost about an hour worth of coding, when I was refactoring some class names, and one failed saying something like "cannot analyze the symbol.."; the entire file had simply jumped to a very old snapshot of the file. (I used ctrl+s during all changes to make sure there were no unsaved changes).
I was able to randomly recreate a similar but much smaller jump, several times, on the following code:
enum XPerfStatsType {ThreadPerfStats=1, MsgPerfStats, MAX_TYPES};
class XPerfStats
{
public:
XPerfStats(){ m_XPerfStatsType = 0; }
virtual void Reset() = 0;
virtual void DumpPerfStats() = 0;
int m_XPerfStatsType;
};
1. hit alt+shift+R and refactor class "XPerfStats" to "BasePerfStat" and hit Enter (i.e. without opening the refactor dialog)
2. hit ctrl+s just to make sure.
3. now refactor enum "XPerfStatsType" to "PerfStatType" the same way.
4. randomly sometimes step 3 fails saying "cannot analyze the symbol.."; and immediately both the enum and class name jumps back to the original.
Is there a stronger way (than ctrl+s) to commit/flush all changes and ensure that nothing can rollback to an earlier point than this under any circumstance?
|
|
|
Powered by
FUDForum. Page generated in 0.05257 seconds
Home