Community
Participate
Working Groups
If you move or rename a folder it automatically changes the file contents. This is a really annoying feature which created a ton of work for me now. now I have over _FIVE HUNDRED_ files in which the include paths look ALL like this: #include "../../../../../project_folder/n_ws/folder/src/conf/header.h" instead of before: #include "conf/header.h" Just to mention: THIS SUCKS A LOT. Fix this in the following ways please: Make at least a checkbox (which is by *default* disabled) saying something like "update include paths inside files" And do not update paths to a greater folder depth they actually were, then this feature could probably work like it should. So now I am going take some time to clean this F***IN MESS up, because I did not realize in first place that this happened ... already checked in git plus multiple commits above ... Nice job...not... Regards, Christian
I can confirm this behavior and it's really annoying. Would be great if the proposed checkbox solution could be realized.
Behavior confirmed here as well. There are several use cases where this behavior is fine, but there are also _MANY_ cases where this is completely undesirable. Please-Please add a checkbox for disabling this :-) BR Fink
Throwing in my two cents here. I also would like to see this "feature" made optional via a checkbox. Renaming a folder containing some sources rewrote EVERY file in that folder, making the includes something like "../../../../../../path/all/the/way/back/to/header.h"
