quick refactor/rename causes entire file to be marked as changed -- V 17.0.2

[davehohl]

If I use the quick refactor feature to rename something, after saving the changes every line in the file is marked with the "line inserted" color in the left side of the edit window.

SlickEdit 2012 (v17.0.2.0 32-bit)

Licensed number of users: Single user
License file: C:\ProgramData\slickedit\17\slickedit.lic

Build Date: August 09, 2012
Emulation: CUA

OS: Windows 7
OS Version: 6.01.7601  Service Pack 1
Memory: 65% Load, 2182MB/3318MB Physical, 3311MB/6635MB Page File, 279MB/2047MB Virtual
Shell Info: C:\Windows\system32\cmd.exe /q
Screen Size: 1920 x 1200

Project Type: Cpp
Language: .cpp (C/C++)

Installation Directory: C:\Program Files\SlickEditV17.0.2\ (non-removable drive,NTFS,232209MB free)
Configuration Directory: U:\MyDocs\My SlickEdit Config\17.0.2\ (remote,NTFS,183862MB free)

[JeffB]

Is it possible that you had white space at the end of the lines?   In my case, I have VS configured to remove white space only at the end of lines I've changed.  There is an outstanding bug in refactoring where it seems to ignore this setting and remove all EOL white spaces from any lines.

Jeff

[davehohl]

Hi, Jeff,

Thanks for the idea. I tried refactoring in a file where I checked several lines to make sure there was no white space at the end, and they still ended up getting marked as changed. And the other interesting thing is that the color used indicates a line insertion, not just a modification. Very weird.

[davehohl]

Am I the only one seeing this? It is still happening with hotfix 9.

[chrisant]

Hasn't this always been the case, since refactor/rename was introduced?

SE typically reloads a buffer after these kinds of operations.  This isn't the only feature where this happens.  I don't think this is a quick fix kind of thing, I suspect it's more like rewriting core infrastructure and could be an expensive thing to do.  Just saying I wouldn't expect a quick fix in a hotfix for this.

[davehohl]

Hasn't this always been the case, since refactor/rename was introduced?

I tried this in V16, and yes, you are correct, it was there before. I guess I never noticed it because I did not have the modified lines feature enabled under V16.

Still, it is annoying, albeit not a major issue.