User forums > Using Code::Blocks

Bug Report: [#18755] C::B hangs for 20 seconds while opening large project...

<< < (9/20) > >>

MortenMacFly:
...btw: having re-applied my original patch, most things work, except UNC handling. (Did I mention that UNC sucks, btw?! ;D)

Jenna:

--- Quote from: MortenMacFly on October 24, 2012, 09:34:03 am ---...btw: having re-applied my original patch, most things work, except UNC handling. (Did I mention that UNC sucks, btw?! ;D)

--- End quote ---
But this will lead to the slowdown again.
Checking for an UNC pat should not be too hard.

And for the other issue (if the projectfile itself is aved on a different volume, after calculating the commonTopLevelPath):
does saving the project on a different path trigger the recalculating of the commontopLevelPath (and rebuilding the project tree) ?
If not, the error is there.
I hope I find the time to look into it today.

Jenna:
Can you test the attached patch ?
It's not tested in any case by me (just a quick hack), so be careful with real projects.

MortenMacFly:

--- Quote from: jens on October 24, 2012, 10:26:34 am ---But this will lead to the slowdown again.

--- End quote ---
True. But my trial was to see if the changes of dmoore actually caused the mis-behaviour.


--- Quote from: jens on October 24, 2012, 10:26:34 am ---does saving the project on a different path trigger the recalculating of the commontopLevelPath (and rebuilding the project tree) ?

--- End quote ---
Well it works for me now (I'll double-check in a minute) - so my guess is that the error was in the patch...


--- Quote from: jens on October 24, 2012, 11:23:52 am ---Can you test the attached patch ?

--- End quote ---
...will do. But it may take some time again.

dmoore:

--- Quote from: MortenMacFly on October 24, 2012, 09:31:58 am ---
--- Quote from: jens on October 24, 2012, 09:25:06 am ---But what if the projectfile (*.cbp) has an UNC path ?

--- End quote ---
You mean if the project file itself is on an UNC path? In that case, there is no common top-level path and all files should use absolute file names / path's for all purposes. However, this is a very special case.

--- End quote ---

what about if everything is on the same UNC path (project and project files). Are you suggesting that the files in this project should always be treated as absolute? (I hope not.)

Navigation

[0] Message Index

[#] Next page

[*] Previous page