The 02 February 2009 build (5432) is out.

[Jenna]

Hi guys,

Thank you for the efforts making the CodeBlocks perfect.

I've found one bug here, ->
The CodeBlocks can't run more than one instance even though the option (Allow only one running instance) has been removed.

Uncheck "Use an already running instance instead of starting a new one (if possible)" also, or start C::B with parameter "-ni" (linux) or "-nd" (windows).

[Grom]

When we are going to have a new relize with automatic update? :?

[Jenna]

When we are going to have a new relize with automatic update? :?

Possibly when you provide a patch for this and it get accepted.

[dmoore]

When we are going to have a new relize with automatic update? :?

get on a debian system and you can have automatic updates of every nightly.

[Sunyata]

I didn't notice that option.... :oops: Now it works. Thank you very much !

Hi guys,

Thank you for the efforts making the CodeBlocks perfect.

I've found one bug here, ->
The CodeBlocks can't run more than one instance even though the option (Allow only one running instance) has been removed.

Uncheck "Use an already running instance instead of starting a new one (if possible)" also, or start C::B with parameter "-ni" (linux) or "-nd" (windows).

[ollydbg]

Change the management panel problem?
snap1:
If I want to view the "Symbols" panel. I should firstly press the right triangle button.

snap2:
Then, the "Projects" panel is still active below. So I should click on the "Symbols" panel stub to view it.

snap3:
The "symbols" was active.

My question: I need to press twice to change the panel. Why not just press once on right triangle button to change to the next panel directly to avoid the extra click?


[attachment deleted by admin]

[Grom]

What about new relise? Do you have any road map?

[XayC]

Hi guys,

Thank you for the efforts making the CodeBlocks perfect.

I've found one bug here, ->
The CodeBlocks can't run more than one instance even though the option (Allow only one running instance) has been removed.

Uncheck "Use an already running instance instead of starting a new one (if possible)" also, or start C::B with parameter "-ni" (linux) or "-nd" (windows).

I think this should be considered as a bug.
Is it intended to have the DDE server blocking a second instance of C:B? Is there any good reason for it?

I remember it was working before the changes to the DDE server (i.e. Code::Blocks 8.02), and those changes were made to fix other problems.
Regards, XayC

[Jenna]

Hi guys,

Thank you for the efforts making the CodeBlocks perfect.

I've found one bug here, ->
The CodeBlocks can't run more than one instance even though the option (Allow only one running instance) has been removed.

Uncheck "Use an already running instance instead of starting a new one (if possible)" also, or start C::B with parameter "-ni" (linux) or "-nd" (windows).

I think this should be considered as a bug.
Is it intended to have the DDE server blocking a second instance of C:B? Is there any good reason for it?

I remember it was working before the changes to the DDE server (i.e. Code::Blocks 8.02), and those changes were made to fix other problems.
Regards, XayC

The DDE-Server on windows still works as before, if you uncheck "Use an already running instance instead of starting a new one (if possible)", at least on my system.
So I think it's not a bug.

Maybe the option can be disabled by default, but that's more or less a matter of taste.

[XayC]

The DDE-Server on windows still works as before, if you uncheck "Use an already running instance instead of starting a new one (if possible)", at least on my system.
So I think it's not a bug.

Maybe the option can be disabled by default, but that's more or less a matter of taste.

Yes, you are right. I was confusing that option with the old "allow only one instance". :oops:
Thanks, for pointing that.

Regards, XayC

[emptymind]

In new build don't work commands from custom makefile. Bug?

[Jenna]

In new build don't work commands from custom makefile. Bug?

What exactly do you try, and what does not work ?

Custom makefile using has improved a lot and output might have changed.
See this thread: http://forums.next.codeblocks.org/index.php/topic,9966.0.html.

You will only see the commands run by make, if you set "Compiler logging" to "full commandline", and a build is only done, if it is needed.
By default you only see messages like "Using makefile: makefile.unx" or "Nothing to be done".

[emptymind]

When silent build field is empty but field make build/target = make all makefile don't run
Output (using rebuid):
-------------- Clean: Release in USB_Freq ---------------

Cleaned "USB_Freq - Release"

-------------- Build: Release in USB_Freq ---------------

Using makefile: makefile
Done.

When i type in silent build make all  rebuild feature work correctly.

[Jenna]

To see the makefile commands, you have to change "Settings -> Compiler and debugger... -> Global compiler settings -> <the compiler you use> -> Other settings -> Compiler logging:" to "Full command line".

Custom makefiles now have outputs like "normal" compilation.

The build without output ("Task description") is done with the silent build command.

[emptymind]

I see. Thank you for help.