The 12.11 RC2 (23 November 2012 build 8598) is out.

[rwxdfbb]

on this version, I can see nothing when I open some exist files.

[oBFusCATed]

rwxdfbb: examples or it didn't happen! 

[huzhongshan]

on this version, I can see nothing when I open some exist files.

I just met this. It may be caused by file encoding. I use visualstudio to open the .cpp file , it complains some encoding problem ,and convet it . Then I reopen the cbp in codeblocks , the cpp file can be openned. ( the old encode maybe gb3212 (chinese encoding))

[ptolomey]

The Source formatter doesn't work for me on Code::Blocks 12.11 RC2 (23 November 2012 build 8598)
I use Ubuntu 12.04, 32 bit.

What exactly does not work? Steps to reproduce? It works fine here.

Just saying that "something does not work" is not really helpful you know...

All automatic format functions are disabled.
For example, when I insert braces to define method body I get something like this:

Code

 void method()
{}

Instead what it has to be

Code

void method()
{
          
}

The problem appeared after upgrade of Code::Blocks from RC1 to RC2

[Alpha]

The problem appeared after upgrade of Code::Blocks from RC1 to RC2

The Code::Blocks repository for Ubuntu linux is ppa: https://launchpad.net/~pasgui/+archive/ppa/

I checked into this ppa, and it appears that the most recent build does not contain the SmartIndent* plugins (lost during packaging??).

[MortenMacFly]

The problem appeared after upgrade of Code::Blocks from RC1 to RC2

That is strange because we didn't even touch this component between these builds. Do you really mean the astyle based source formatter, or do you mean "AutoBrace" features or alike form the editor?

[carra]

I have found a really annoying bug! I launch C::B, open some source file (any that is long enough to need a vertical scroll bar in the editor), start writing at some point in the file... and then for each keypress that writes a character, the viewer scrolls 1 line!

In some cases it scrolls up, in others down. I can't predict in what cases it scrolls in which direction.

Can this be caused by reusing default.conf from earlier nightlies? Everything else seems to work fine...

[MortenMacFly]

Can this be caused by reusing default.conf from earlier nightlies? Everything else seems to work fine...

Yes. But this can be disabled in the EditorTweaks options, just not in this specific version (its already fixed in trunk). Please disable the EditorTweaks plugin for now if it drives you nuts.
Alternatively wait for the next nightly / release or compile yourself.

BTW: This has been reported several times already, maybe you search before you post next time.

[ptolomey]

Do you really mean the astyle based source formatter, or do you mean "AutoBrace" features or alike form the editor?

The AutoBrace feature was only example of what is happens. All auto formatting features are disabled in Code::Blocks RC2 from Linux Ubuntu repository: https://launchpad.net/~pasgui/+archive/ppa/

[squalyl]

Hello all,

long time I did not get by there, and I see a release! Nice!

However:

ALL CodeBlocks nightlies up to now have had a very simple but annoying bug with SDCC, so it's time to fix that I guess.

OLD revisions of SDCC used a "rel" extension for object files, which is reflected in this compiler settings.

All recent SDCC releases have now been using "o" for object files.

Can you update that please? There's no chance that anyone will still use such an old SDCC release!

Thanks for codeblocks, it's my daily tool for 3 compilers: mingw, sdcc, and arm-none-eabi using the official arm embedded toolchain (which is not supported yet, so I just change compiler names in "GNU ARM Compiler".)

Sorry for asking this from nowhere, but I guess a RC is the proper moment to do that request

Regards

[Folco]

I compiled my own copy of C::B from SVN (after RC2 release), and I get the same wrong behaviour with the source formater.

I compile all plugin, under Linux Mint 13. I had not these troubles with RC1.

Sorry to not be more precise, I'm totally overloaded at work this week (and tomorrow too...).

[scarphin]

Hello all,

long time I did not get by there, and I see a release! Nice!

However:

ALL CodeBlocks nightlies up to now have had a very simple but annoying bug with SDCC, so it's time to fix that I guess.

OLD revisions of SDCC used a "rel" extension for object files, which is reflected in this compiler settings.

All recent SDCC releases have now been using "o" for object files.

Can you update that please? There's no chance that anyone will still use such an old SDCC release!

Thanks for codeblocks, it's my daily tool for 3 compilers: mingw, sdcc, and arm-none-eabi using the official arm embedded toolchain (which is not supported yet, so I just change compiler names in "GNU ARM Compiler".)

Sorry for asking this from nowhere, but I guess a RC is the proper moment to do that request

Regards

You can change that by hand. Go to settings->compiler settings->choose sdcc as selected compiler->other settings tab->advanced options->others tab->object file extension->o

[squalyl]

Hello, yes thank you, I already know that, I'm not blocked because of that, I'm a "newcomer" on the forum but I've been using codeblocks since 2008.

What I'm asking for is to make "o" the default for SDCC object files because "rel" has been totally irrelevant for months.

So instead of having to change that on each and every new codeblocks setup (I'm following the nightlies so that's more often that you think), it would be nice to integrate the fact that, yes, sdcc has indeed changed "rel" to "o" for object files a long time ago, so "rel" in this place is useless.

as a supplementary annoyance, I have to restart codeblocks to take the new setting into account, which (of course) almost always happens when I have already 10 opened files in the editor.

regards!

[Alpha]

What I'm asking for is to make "o" the default for SDCC object files because "rel" has been totally irrelevant for months.

Patch changing defaults in XML compiler branch:

Code

Index: src/plugins/compilergcc/resources/compilers/options_sdcc.xml
===================================================================
--- src/plugins/compilergcc/resources/compilers/options_sdcc.xml	(revision 8640)
+++ src/plugins/compilergcc/resources/compilers/options_sdcc.xml	(working copy)
@@ -25,7 +25,7 @@
     <Switch name="linkLibs"                value="-l"/>
     <Switch name="defines"                 value="-D"/>
     <Switch name="genericSwitch"           value="-"/>
-    <Switch name="objectExtension"         value="rel"/>
+    <Switch name="objectExtension"         value="o"/>
     <Switch name="needDependencies"        value="true"/>
     <Switch name="forceCompilerUseQuotes"  value="false"/>
     <Switch name="forceLinkerUseQuotes"    value="false"/>

... and in trunk:

Code

Index: src/plugins/compilergcc/compilerSDCC.cpp
===================================================================
--- src/plugins/compilergcc/compilerSDCC.cpp	(revision 8640)
+++ src/plugins/compilergcc/compilerSDCC.cpp	(working copy)
@@ -67,7 +67,7 @@
     m_Switches.linkLibs = _T("-l");
     m_Switches.defines = _T("-D");
     m_Switches.genericSwitch = _T("-");
-    m_Switches.objectExtension = _T("rel");
+    m_Switches.objectExtension = _T("o");
 
     m_Switches.needDependencies = true;
     m_Switches.forceCompilerUseQuotes = false;

[Alpha]

The problem appeared after upgrade of Code::Blocks from RC1 to RC2

That is strange because we didn't even touch this component between these builds. Do you really mean the astyle based source formatter, or do you mean "AutoBrace" features or alike form the editor?

The Code::Blocks repository for Ubuntu linux is ppa: https://launchpad.net/~pasgui/+archive/ppa/

I checked into this ppa, and it appears that the most recent build does not contain the SmartIndent* plugins (lost during packaging??).

The AutoBrace feature was only example of what is happens. All auto formatting features are disabled in Code::Blocks RC2 from Linux Ubuntu repository: https://launchpad.net/~pasgui/+archive/ppa/

Has anyone yet sent a message to let pasgui know the packaging was faulty (missing the SmartIndent* plugins)?