When using the latest build 10.4.1624.0 I have the following issue
When using the refactor->rename feature via the VA outline window a second rename will bring up the wrong member in the rename dialog. Here are the steps to reproduce this.
Create a new C++ project and add a class called RenameClassTest.
class RenameClassTest { public: RenameClassTest(void); ~RenameClassTest(void);
int getInt() const {return m_nInt;}
long getLong() const {return m_lLong;}
double getDouble() const {return m_dDouble;} protected: int m_nInt; long m_lLong; double m_dDouble; };
Open up a header file and in the outline window right click on one of the m_nInt member and select refactor->rename. Change it to m_nInt1.
Now right click on m_dDouble and select refactor->rename. The name that comes up in the rename dialog is not m_dDouble for me it is getInt.
I am seeing the same effect here. Thank you for the clear description.
case=10502
For me, if I Cancel the incorrect Rename dialog and trigger Rename again on "m_dDouble" then VA searches for the correct symbol, which is something.
Alternatively changing to a different file, and then changing back to this file after the first rename stops this happening. Changing files causes VA Outline to be rebuilt.
Are you talking about a flicker when using remote desktop? Or some other problem?
Remote desktop and flickering is:
case=281
We are currently looking at this, and some other colouring problems as well, but currently no estimate on when this will be addressed. Have you tried turning off VA's colouring and underlining options?