User forums > Nightly builds

The 01 October 2013 build (9378) is out.

<< < (5/7) > >>

Alpha:

--- Quote from: Alpha on October 13, 2013, 05:47:35 pm ---Can you try applying this patch?
[...]

--- End quote ---
I have not noticed problems with this patch, and will commit soon if there are no further comments.  (I would appreciate if someone who has observed problem 2. can report whether or not this patch resolves it.)

Randajad:
After updating from 9158 codeblocks drop all compiler settings.
It's too sad, will stay on 9158.

White-Tiger:
what do you mean exactly? I'm on 9393 and it's working fine* :P
(and I've got lots of custom but still mandatory compiler settings... -m32, -m64, -flto, -static, -fPIC etc.)

*besides those nasty crashes every C::B build with code-completion includes^^

CrispiestMushroom:
Ahem. Greetings all, I have an announcement to make. I can get C::B to consistently crash by opening the watch properties while a watch is being evaluated. I'm not sure if it's just me, but If anyone is interested in the steps to reproduce said phenom, or would just like to observe the action, I will be making a demo video sometime today. That is all.

ToApolytoXaos:

--- Quote from: Static on October 13, 2013, 11:42:46 am ---What about #include filenames completion? This feature seems to work sometimes and sometimes it doesn't.
Assume I want to include the file at "../dialogs/CustomDialog.h"
So, I type:
#include "../d" (note the closing quote mark)
and here comes CC suggesting "../dialogs/CustomDialog.h". I press 'enter' and get
#include "../dialogs/CustomDialog.h"" (extra quote mark)
or even
#include "../d../dialogs/CustomDialog.h" (my input wasn't overwritten)
But sometimes headers completion works perfectly.
Should this be reported as a bug?

--- End quote ---
I have a similar issue with header files. For example, if I have typed <ios> by mistake and take my cursor inside header name, and continue typing from 's', it will pop up options like iosfwd and iostream. When I choose the latter by pressing the tab key, it automatically adds an extra > character.

Is this an expected behavior, or a bug?

Cheers.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version