User forums > Using Code::Blocks

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

<< < (19/20) > >>

rickg22:

--- Quote from: MortenMacFly on November 04, 2012, 05:22:17 pm ---It is tested against UNC path's again and also against different project tree layout options?

--- End quote ---

My code is magically sealed inside an #ifdef; unless you summon it with the define above, your code will be the one running.

Anyway, you've been the most thorough tester so far. Can you provide us with a test suit (zipped .cbp's and installation instructions) so that we can easily test these modifications?



--- Quote ---BTW: I had a few days off and I am trying to catch up - what's with the other patches in the other posts o[f this thread? Does this one cover all?

--- End quote ---

All my patches? Yes. It's built against rev 8502.


--- Quote ---Oh - and btw: I don't know if I personally would sacrifice the read-only flag for speed. When working with SVN controlled projects its often vital to see if a file is write-protected (i.e. locked). So I would definitely like to see a global option to be able to always have this check on in one place.

--- End quote ---

Yup, that's how it's coded. One global check. Perhaps we could add an item under the Project submenu with the title "Check for missing or write-protected files", that basically does the same thing. And we could modify the entry in the configuration with a dropdown menu: "Check for missing or readonly files" with the options "Always", "Never", "Only for small projects" (this option would let the user specify a project size). Or who knows, explicitly add it under the Project submenu?

Anyway, my patch is working and using your code, so it's safe to put in trunk.

MortenMacFly:

--- Quote from: rickg22 on November 04, 2012, 05:48:24 pm ---Anyway, you've been the most thorough tester so far. Can you provide us with a test suit (zipped .cbp's and installation instructions) so that we can easily test these modifications?

--- End quote ---
I've explained and enumerated it already in a previous message in this thread. There is no test suite - sorry. But I can do, if I find the time. For now I just have applied the patch to see...

Concerning that, I've spotted two issues:
- The config option is mis-spelled "mising" instead of "missing" (in all three places).
- It does not compile under wx2.9 because you are using the obsoleted (and wrong) c_str() method of wxString. You'll need to change it to wx_str().


--- Quote from: rickg22 on November 04, 2012, 05:48:24 pm ---Yup, that's how it's coded. One global check.

--- End quote ---
That's good to hear. :-) As I said - I've applied it in my local copy... lets see if it nukes all my HDD. ;D

dmoore:
So if Rick's patch is on ice for a bit, why don't you also take my patch from a few posts back, which should take care of the slowdown for projects with normal layouts. (Not as elegantly as Rick's)

MortenMacFly:

--- Quote from: dmoore on November 07, 2012, 01:16:13 pm ---So if Rick's patch is on ice for a bit,

--- End quote ---
I wouldn't say its on ice. I think Rick can commit as the changes in question are indeed hidden with a #define for power users and further testing.
I can take care of the compilation stuff in wx29/64 bit (which I have done in my local copy already).

The only thing I am kind of "waiting" for is that somebody tells me it still works with UNC path's and so on... But I'm afraid I have to see myself as I am surrounded by Linux devs... huh! :'(

dmoore:

--- Quote from: MortenMacFly on November 07, 2012, 01:34:26 pm ---
--- Quote from: dmoore on November 07, 2012, 01:16:13 pm ---So if Rick's patch is on ice for a bit,

--- End quote ---
I wouldn't say its on ice. I think Rick can commit as the changes in question are indeed hidden with a #define for power users and further testing.
I can take care of the compilation stuff in wx29/64 bit (which I have done in my local copy already).

The only thing I am kind of "waiting" for is that somebody tells me it still works with UNC path's and so on... But I'm afraid I have to see myself as I am surrounded by Linux devs... huh! :'(

--- End quote ---

I regularly use windows... but at work where I have very limited time... and the servers don't have accessible UNC paths.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version