projectfile.h||In constructor 'ProjectFile::ProjectFile(cbProject*)':|
projectfile.h|237|warning: 'ProjectFile::project' will be initialized after [-Wreorder]|
projectfile.h|195|warning: 'GlobId ProjectFile::globId' [-Wreorder]|
projectfile.cpp|26|warning: when initialized here [-Wreorder]|
projectmanagerui.o||In function `ZN16ProjectManagerUI13OnManageGlobsER14wxCommandEvent':|
C:\Codeblocks\src\src\projectmanagerui.cpp|1657|undefined reference to `ManageGlobsDlg::ManageGlobsDlg(cbProject*, wxWindow*, int, wxPoint const&, wxSize const&)'|
C:\Codeblocks\src\src\projectmanagerui.cpp|1657|undefined reference to `ManageGlobsDlg::~ManageGlobsDlg()'|
C:\Codeblocks\src\src\projectmanagerui.cpp|1657|undefined reference to `ManageGlobsDlg::~ManageGlobsDlg()'|
My point of view is, that the project file is like a make file. You have to modify a makefile if you add source files to be able to build it.
If you do not add them to the project we have some problems:
1) you can not modify properties of them: Only build with certain build targets ecc.
2) I had other problems with the old implementation, i can not remember any more exactly (it is a 3 years), i think code completion did not work correctly...
We have discussed this with the problems of the original implementation here: http://forums.codeblocks.org/index.php/topic,22783.msg154862/topicseen.html
My opinion on this: This feature was never/seldom used by user before, because it had no ui/documentation. So the risk of breaking some project files is minimal. I also pointed this out in the announcement post (https://forums.codeblocks.org/index.php/topic,25276.0.html). Now it has UI and documentation and we can expect it to be used... I for example need it for an upcoming plugin i currently am working on...
If you are absolutely against this implementation i can try to look into it and add some flag for old and new behavior?
I will look into the problems with the ids. Thank you for testing and pointing it out.
Is it also not desired, that the globs get automatically reloaded when new files are added in the directory? So no automatic reloading?
After commiting this feature files can't be removed from projects (I am not using globs). See this forum thread.fixed in trunk
since your repo/clone does not contain clangd clienti do not understand? This is in the git repo, i use it all the time...
please activate this on trunk if you canis in trunk, with many other fixes...
The diff is due to the following options being saved in the cbp file:I do not see any "easy" possibility to not add this to the project glob project file entry, and keep the features. I would have to store if this were in the origin project file and save only if there. But this would make the code a lot more complicated and not really dev friendly...
* addToProject=0
* id = some magic value
* wildcard now after the recursive
when opening the project file once more, and closing it, CB again says there are changes,Can you try my last changes? If they do not fix it, can you give me a minimal example project, i can not reproduce it with my test cases...
The files are there, the project is open, a file is open in the editor pane, edit in the file, save --> editor gets closed.I can not reproduce this...
One thing I have noticed, that after a compile, or other actions, CB crashed a a lot since I applied the first patch.yea, this are my worries.... The problem is i can not test this as elaborate as you, because i can not reproduce... If you could attach a debugger or a trace it would be nice. I suspect the code completion plugin? Can you try to disable it and see if the crashes repeat?