// NOTE: it actually forces reparsing of workspace
void NativeParser::ForceReparseActiveProject()
{
m_Parser.Clear();
UpdateClassBrowser();
ProjectsArray* projects = Manager::Get()->GetProjectManager()->GetProjects();
for (size_t i = 0; i < projects->GetCount(); ++i)
{
AddParser(projects->Item(i), false);
}
}void NativeParser::ForceReparseActiveProject()
{
m_Parser.Clear();
UpdateClassBrowser();
AddParser(Manager::Get()->GetProjectManager()->GetActiveProject(), false);
}Note: the comment:No. Consider a (very common) setup of a workspace that consists of 1.. n projects where 1..(n-1) are libraries used by the main (n'th) application. In the main application you surely want to have CC for the libraries. That's why we initially implemented it the way it is now. On request of users, btw.!
/ /NOTE: it actually forces reparsing of workspace
Should it just reparse the active project?
I understand and see the utility of it. However, I was expecting that the setting in the symbols tab -> View: "Active project's symbols | All local symbols (workspace) | ..." should also apply to the CC itself. Meaning that if I set it to "Active project" then I get suggestions for the active project only, but if I set to "workspace" then I have all projects...Note: the comment:No. Consider a (very common) setup of a workspace that consists of 1.. n projects where 1..(n-1) are libraries used by the main (n'th) application. In the main application you surely want to have CC for the libraries. That's why we initially implemented it the way it is now. On request of users, btw.!
/ /NOTE: it actually forces reparsing of workspace
Should it just reparse the active project?
One possibility I see is to make it configurable. Patches in that direction are welcome.
@daniloz (http://forums.codeblocks.org/index.php?action=profile;u=11641)That patch is not yet perfect, I will continue to focus on this issue, and try to find a better solution.
Loaden has a patch to let the parser generate one TokensTree per project. I will asked him to publish to the CB forum soon. :D
I understand and see the utility of it. However, I was expecting that the setting in the symbols tab -> View: "Active project's symbols | All local symbols (workspace) | ..." should also apply to the CC itself. Meaning that if I set it to "Active project" then I get suggestions for the active project only, but if I set to "workspace" then I have all projects...Note: the comment:No. Consider a (very common) setup of a workspace that consists of 1.. n projects where 1..(n-1) are libraries used by the main (n'th) application. In the main application you surely want to have CC for the libraries. That's why we initially implemented it the way it is now. On request of users, btw.!
/ /NOTE: it actually forces reparsing of workspace
Should it just reparse the active project?
One possibility I see is to make it configurable. Patches in that direction are welcome.
What do you think?