Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Feature Requests
 allow selection of public/private/protected...
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

shiihs
New Member

6 Posts

Posted - Nov 27 2013 :  03:37:27 AM  Show Profile  Reply with Quote
Hello,

Please consider allowing selection of public/private/protected in operations like:

extract method
create declaration
create from usage
add member

I've been using other products who offer this functionality (e.g. QtCreator has it), and I miss the feature in visual studio+visual assist which I use in my day job.

feline
Whole Tomato Software

United Kingdom
15984 Posts

Posted - Nov 27 2013 :  6:25:13 PM  Show Profile  Reply with Quote
We are currently trying to keep the refactoring dialogs simple and fast to use. The design idea is that the operations can be chained together to produce the result you want.

Are you aware that you can quickly and easily move items from one visibility to another with VA Outline? You can drag with the mouse or use cut and paste. Also, in C++ you can easily have more than one public and private block in a class.

http://www.wholetomato.com/products/features/vaoutline.asp

zen is the art of being at one with the two'ness
Go to Top of Page

shiihs
New Member

6 Posts

Posted - Nov 28 2013 :  08:37:31 AM  Show Profile  Reply with Quote
Hello,

Thanks for reading and replying.

I am aware about the outline features in VA. The source of my annoyance comes from having to "clean up" after VA's back all the time. (i.e. move stuf from whatever insert location was used to a private/public/protected section). It breaks "the flow".

I agree that the current menus are quite loaded, but perhaps it would make sense to make the menu configurable? Allow people to choose what to see in the top-level menu, and allow them to hide the less often used functionality in a submenu (similar to TortoiseSvn e.g.).

As for multiple blocks of public/private/protected:
I'm aware of that.

I think if VA could just add new things to either the first or last such block in the file, it might cover >50% of real-life use cases, whereas the current insert location seems a bit random at best, and probably works correctly in only 10% of the use cases? (Ok that's a bit harsh, probably because I don't know the current insert location selection logic. What is the current VA rule for choosing an insert location?

Go to Top of Page

feline
Whole Tomato Software

United Kingdom
15984 Posts

Posted - Nov 28 2013 :  1:44:41 PM  Show Profile  Reply with Quote
Would selecting the visibility level in the dialogs really fix the issue?

Longer term we are hoping to make the insert logic try and place the new function next to the "current" function in the cpp file, using this as a reference point:

case=12454

Its a good plan, but also rather assumes that the ordering of functions in the header and cpp file is largely the same to begin with, an assumption that rarely holds in reality. I am wondering if this would make a more direct difference, or if this is just a nice but less important addition.

zen is the art of being at one with the two'ness
Go to Top of Page

sean
Whole Tomato Software

USA
2641 Posts

Posted - Feb 13 2015 :  8:15:26 PM  Show Profile  Reply with Quote
case=12454 is fixed in build 2059
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2019 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000