| T O P I C R E V I E W |
| SnowBoy |
Posted - Jun 13 2006 : 04:27:30 AM
The "Find References" command doesn't work on my project. Every time I click on it nothing happens. However, when I click on the "Rename" command (which I think it's related to the "Find References"), the list of all references to the selected symbol pops up.
Furthermore the refactoring menu sometimes doesn't appear and I get the message "Refactoring not Available for Symbol" (this happens on the fields of the class when I try to rename one of them).
I work in C# and my machine data is:
VA_X.dll file version 10.3.1522.0 built 2006.06.08
Licensed to:
VA X: ... (1-user license) Support ends 2007.02.10
VAOpsWin.dll version 1.3.3.2
VATE.dll version 1.0.5.7
DevEnv.exe version 7.10.3077.0
msenv.dll version 7.10.3077.0
Font: Courier New 12(Pixels)
Comctl32.dll version 5.82.2900.2180
Windows XP 5.1 Build 2600 Service Pack 2
2 processors
Platform: Win32
Stable Includes:
C:\\Programmi\\Microsoft Visual Studio .NET 2003\\Vc7\\include;
C:\\Programmi\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\include;
C:\\Programmi\\Microsoft Visual Studio .NET 2003\\Vc7\\PlatformSDK\\include\\prerelease;
C:\\Programmi\\Microsoft Visual Studio .NET 2003\\Vc7\\PlatformSDK\\include;
C:\\Programmi\\Microsoft Visual Studio .NET 2003\\SDK\\v1.1\\include;
Library Includes:
C:\\Programmi\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\src\\mfc;
C:\\Programmi\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\src\\atl;
C:\\Programmi\\Microsoft Visual Studio .NET 2003\\Vc7\\crt\\src;
I've installed also the following IDE add-ins:
- Kings Tools (compiled by myself);
- Test Driven (latest release).
It's possibile to add a "Document Field" command that works on the selected class field? |
| 10 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Jun 19 2006 : 5:38:49 PM
have you considered using two autotext rules, with the same shortcut, perhaps "//-" or "//*" ?
then when you type the shortcut you will be given a listbox asking you to select which autotext rule you wish to enter. one will be the short form and the other the longer form.
since you are looking at a simple fixed form, that does not depend on the details of the variable declaration refactoring is a bit overkill  |
| SnowBoy |
Posted - Jun 19 2006 : 02:31:03 AM
For my comments I use the following formats:
/// <summary>
/// Field documentation
/// </summary>
or
/// <summary>
/// Field documentation
/// </summary>
/// <remarks>
/// Extensive field documentation (used only sometimes)
/// </remarks>
|
| feline |
Posted - Jun 17 2006 : 1:21:20 PM
that makes a degree of sense. are you after some specifically formatted comment for the member variables?
i am trying to work out how well this fits into refactoring, or if it fits into something else better.
currently there is one autotext rule, which is used for documenting functions. this comment format is probably not suitable for commenting member variables. personally i just use a trailing comment, so for that a refactoring option seems overkill.
|
| SnowBoy |
Posted - Jun 16 2006 : 07:58:26 AM
I mean something like this:
/// Class documentation
public class ClassName
{
/// Field documentation
private string Text;
}
I've suggested the "Document Field" command because it makes the action more contextual to the refactoring stage (so I could document fields and methods at the same stage with the same actions...).
However it's possibile to get the same results even with the "autotext" command.
PS: Sorry for the delay, I cannot check the forum in the past days. |
| feline |
Posted - Jun 14 2006 : 6:05:06 PM
that makes more sense. when you say "field" what are you referring to? i know a bit of C# but not a massive amount. do you mean member variables, or something else?
surely for a member variable there is not really anything to generate. in C++ i use comments like:
int m_nSize ///< tracks how big this item has become
to add doxigen comments to member variables. since there is nothing in the comment that cares about the member variable name i use an autotext rule for this. |
| SnowBoy |
Posted - Jun 14 2006 : 02:42:47 AM
With a "Document Field" (that appear into the refactoring menu) command I mean a function that works like the "Document Method", but on the selected field instead of the method of the class.
In this way it's possible to add the comments so they could be used by DoxyGen to create the documentation. |
| feline |
Posted - Jun 13 2006 : 5:33:38 PM
quote:
Originally posted by SnowBoy
What about the "Document Field" command?
i don't understand the question. there is a "Document Method" function. |
| SnowBoy |
Posted - Jun 13 2006 : 11:04:39 AM
All right! Something get wrong with the previos installation.
I've uninstalled everything and installed the latest release and the things work right. Even the message "Refactoring not Available for Symbol" doesn't appear in the wrong place.
Thanks
What about the "Document Field" command?
|
| SnowBoy |
Posted - Jun 13 2006 : 10:54:43 AM
The function doesn't work even on other projects. Additionally, when I call it from the refactoring menu the window doesn't appear.
However, I've tried to call it from the toolbar and with a shortcut and I found that something get wrong with the installation. In fact the icon for the "Find References Results" command (that's similar to the one for "Find Next by Context") doesn't appear when I try to customize the buttons on the toolbar; even when I try to add a shortcut I can't find the "Find References Results" command in list of commands with prefix "VassistX.". Hence I think that I've get some problem with the installation of the latest release of the VAssistX.
I'll try to make a clean install of the plugin and I'll send the latest results. |
| support |
Posted - Jun 13 2006 : 08:55:04 AM
Is the Find References Results window visible?
Does Find References work in other projects?
We assume you try the toolbar button for Find References. Does the entry in the VAssistX menu work? How about using a shortcut to VAssistX.FindReferences?
|
