void BlaBla::somemethod ()
{
  // bla bla
  |
  // bla bla
}

• Method not declared in class: message box or suggest to create declaration


• Class for method not found: message box with appropriate error


• Found two classes

class BlaBla
{
public:
   void somemethod(int value);   
   void method1();   
...
...
 | void somemethod();   
...
...
   void method2();   
}

• Method not defined: message box or suggest to create definition

• Cycle files that declare selected namespace


• Jump from includes section of header file to includes section of appropriate cpp file


• Jump to class's forward declaration


• Jump between templates with the same name


• ...

quote:

---

Are you familiar with the Hovering Class Browser, the bottom half of VA View? This will show you the class, its functions, and if you turn on:

VA View -> Right Click -> Show current scope when typing

then VA will show you the current function / class while the caret is in the middle of a class.

I know this is not quite the same as what you are describing here.

---

quote:

---

Currently VA does not have sufficient understanding of overloaded functions to do what you are describing here. This is why when you use alt-g on an overloaded function VA will list all of the overloads in the alt-g menu, allowing you to pick the one you want to jump to.

---

quote:

---

Originally posted by feline

The idea of jumping between the declaration and implementation regardless of position in either makes sense, and I have put in a feature request for this:

case=7894

I can see why cycling through the constructors is a useful idea, but really this is just a special case of cycling through all overloads.

A couple of thoughts occur to me here. Firstly if your overloaded constructors are grouped together in the cpp file then next and previous scope is a fast and easy way of moving from one to another, since this lets you move through a file one function at a time:

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

---

quote:

---

A second thought, you may also find VA Outline useful. This is currently in beta, and you need to enable it with a registry key before you can use it:

http://forum.wholetomato.com/forum/topic.asp?TOPIC_ID=6149

It will help you quickly group the overloads within a file, and also can be very useful for navigating through the current file.

---

quote:

---

The position of the alt-g menu has come up before. Short of adding an option the problem is that people who are mouse orientated use the mouse to select the item they want from the menu, so they want the menu to appear where the mouse cursor is. At the same time people who are keyboard oriented want the menu to appear next to the caret, since they will be using the keyboard to move through it.

---

quote:

---

Originally posted by feline

Next and previous scope have the default keyboard shortcuts of Alt+Up Arrow and Alt+Down Arrow, which became second nature to me quite a few years ago

---

quote:

---

VA Outline is proving really rather popular, for obvious reasons. Don't worry, we are continuing to improve this.

---

quote:

---

I have put in a feature request to control the position of the alt-g menu, having the menu appear on the second (or possibly 3rd) monitor is certainly going to be a bit unhelpful for keyboard focussed programmers:

case=7901

---

quote:

---

As for case=7901 I have no idea when this will be done to be honest. We have quite a lot of outstanding bug reports and feature requests, with more arriving all the time. When it is done this thread should be updated with that information, and it will be mentioned in the list of changes for the new build.

---

• position carret on method name


• invoke Visual Studio's comand Go to Declaration, damn - command don't work...


• copy method name


• switch to Header file


• press Ctrl+F


• paste method name


• (sometimes setup match options)


• and what i have: comments, methods from other classes (many classes)


• o miracle i found this!! Navigate to another file... I forgot to drop bookmark. Damn it...
  continue algorithm again

quote:

---

If you want to know about the method and its class then just show VA View, make sure keyboard focus is in the source code, and hover the mouse over a function name, or even a function *call*.

I agree that finding your way around code is important.

Looking at what you are describing the following thoughts come to mind:

* use OFIW to find the file you want - ideal if the file names are related to class names
* use FSIW to find the function or class you want
* when you are in a file use alt-m and just type a bit - a *lot* faster and easier than find, if you are looking for a specific function
* some of the time Find References is going to be what you need

---

quote:

---

case=7901 is not going to help with any of this, all this will effect is the position on screen of the alt-g menu, not its content.

---

• If the mouse position is within the VS IDE window, use this to place the context menu.


• If the mouse position is outside the VS IDE window, then the command couldn't be triggered via the mouse. In that case open the context menu at the caret's position.