Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Technical Support
 Move Implementations to Source File Issues

You must be registered to post a reply.
Click here to register.

Screensize:
UserName:
Password:
Format: BoldItalicizeUnderlineStrikethrough Align leftCenterAlign right Insert horizontal ruleUpload and insert imageInsert hyperlinkInsert email addressInsert codeInsert quoted textInsert listInsert Emoji
   
Message:

Forum code is on.
Html is off.

 
Check to subscribe to this topic.
   

T O P I C    R E V I E W
Kaylx Posted - Mar 01 2013 : 06:01:43 AM
Hi there,

Got a really strange problem, i don't think it's intentional, but every time i've used the forementioned feature it moves all the functions to the cpp file in reverse order. It's really annoying!

For example

class Foo
{
public:
Foo(){}
~Foo(){}
void bar1(){}
void bar2(){}
void bar3(){}
}

becomes

void Foo::bar3(){}
void Foo::bar2(){}
void Foo::bar1(){}
Foo::~Foo(){}
Foo::Foo(){}

Please help. :-/
1   L A T E S T    R E P L I E S    (Newest First)
accord Posted - Mar 01 2013 : 2:29:08 PM
I wasn't able to reproduce the problem using VS2012 update 1 and VA1929.

What Visual Assist and Visual Studio versions are you using?
What method of your sample class do you use the mentioned feature on?
How do you trigger Change Signature? Right click, refactor menu or IDE VAssist -> Refactor menu?
If you click on the class name, Foo, something similar will happen. But VA will display a dialog box with the method names first and you can accept or cancel the request here.
Are you able to reproduce the problem using your sample class, in a clean new win32 test project?

© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000