I fixed one warning. Then another, and on reading I see the first has reverted to the pre-fix state.
Example:
Manually edit "space" to "spacetoken". Then click Fix for the "first" hint.
even if you save after the edit
But if after the edit, I click Refresh, the edit sticks.
So ... after each Fix, shouldn't you automatically Refresh?
BTW I put my code inside backquotes but that did not come out as code.
Option Explicit
(Dang it after editing this, the line above came out as code. Never mind, I'll find out eventually)
try it by indenting with spaces:
'test for Fix regression
Sub testFix()
Dim first As Integer
Dim Space As String
'3 issues found.
'Suggestion: Project name is not specified - (testRD.xlsm) VBAProject., line 1
'Hint: Variable 'first' is declared as Integer - (testRD.xlsm) VBAProject.Module1, line 5
'Warning: Variable 'VBAProject.Module1.space' hides function 'VBE7.DLL;VBA.Strings.Space' - (testRD.xlsm) VBAProject.Module1, line 5
first = 1
Space = "%20"
Debug.Print first, Space
End Sub
If RD is modifying the code, it should re-parse automatically. If you are modifying the code and then tell RD to make another change, then you have RD working off a stale parse tree. There's really nothing we can do about this, it's always been like this.
That said, at this point we should be able to have a quickfix or refactoring first verify whether the module has been modified since the parse tree was built, and abort (?) or re-parse (?) before proceeding.
Most helpful comment
That said, at this point we should be able to have a quickfix or refactoring first verify whether the module has been modified since the parse tree was built, and abort (?) or re-parse (?) before proceeding.