| T O P I C R E V I E W |
| Adequat |
Posted - Aug 08 2017 : 05:17:29 AM
When a new source file, out of the solution, is opened, it gets parsed by VA automatically.
This has advantages and drawbacks.
* Here an advantage: I am using Qt and something I need to browse in the source code. Qt being huge, I don't want to have it fully parsed. Parsing only the file(s) I open, is sufficient and good.
* Here a disadvantage, and even a source of trouble. Regularly I open a past version of a source file. Eg. in my solution, I have foo.cpp but I also open foo.cpp from an older folder, to compare stuff. The two foo.cpp are now parsed by VA, and have similar symbols.
The problem is that when I close the old foo.cpp, VA still remembers it, and I could "goto" old stuff easily, thinking this is the new foo.cpp. This ends up me editing the wrong file. This is bad.
The solution would be: when a file that does not belong to the solution, gets closed, it should be removed from VA memory.
|
| 2 L A T E S T R E P L I E S (Newest First) |
| Adequat |
Posted - Aug 09 2017 : 3:03:29 PM
"Restrict Goto (Alt+G) to active project" is not an option, as my solution is made of multiples modules, each one being a project. I need to goto these projects.
quote:
For Qt, have you considered adding Qt to your stable include directories?
I never felt the need for this.
|
| feline |
Posted - Aug 08 2017 : 08:52:08 AM
When you are being taken to the old version of the file, which VA command or commands are you using? I am thinking that the setting:
VA Options -> Projects and Files -> Restrict Goto (Alt+G) to active project
should help here.
For Qt, have you considered adding Qt to your stable include directories? This way VA will only parse the Qt library when rebuilding the symbol database, the rest of the time we just keep the Qt symbols in hand, to help with coding and navigation.
https://docs.wholetomato.com/default.asp?W213 |
|
|
