The 27 May 2026 build (13855) is out.

[ThierryD]

Today, I try to download this last nightly of CB into WSL2 (Ubuntu 24.04) using Firefox browser (just my choice ...    )

BitDefender AV don't control this 7z archive (YES !), by default stored on "$HOME/Downloads".

Into terminal Ubuntu 24.04, I use command "7z" to extract directly to "/mnt/c/CodeBlocks", ... and BD AV detect like previous downloads an malware, and, like Eckart, link to file "CB_soncole_runner.exe" just decompressed ...

I force BD AV to restore this specific file. 

After that, I run CB (after decompress also two dependencies files with MinGW64 and WX DLL), and result is OK.

I don't know why, CB has been very long time to start ... but (be patient) ..., after I can use last nightly of CB normally.

Story is closed !

Thank's.




 

[MaxGaspa]

I lookfor a setings to get the dark mode using this nightly and Windows 11 25H2. It seems there is no such an option. So can you confirm that dark mode is not supported in Windows 11? Is it possible to enable the dark mode in Windows11? Is a long waited feature....

[gd_on]

You can use C:B in darkmode. At least 2 ways to obtain this :

• Use darkmode for Windows: C::B will follow Windows mode
• Use a small cmd file to force darkmode: This cmd file is something like:
  

Code

REM To force darkmode (if 0 standard color mode, if 1 follow system mode)
set WX_MSW_DARK_MODE=2
codeblocks.exe

Then you can adjust different colors.
In this example, this codeblocks_DarkMode.cmd file is placed where codeblocks.exe is installed.

[MaxGaspa]

set WX_MSW_DARK_MODE=2

Thanks...I wasn't aware of the environment variable WX_MSW_DARK_MODE. Now I set this environment variable and I'm able to switch between the two modes quickly.

[MaxGaspa]

[Main Instruction]
A debugging check in this application has failed.

I've found that deleting the .conf file just one time solved this for me.

Pecan, trying to re-customize my default.conf I think I found the root cause of the issue and so a quick way to fix it. The root cause of the debugging checks is a specific setting

Settings->Environment Settings->Notebooks Appearance->Tab Style

If you set the tab style to Firefox2 or Microsoft Visual Studio 7.1 the debugging checks are raised

Uisng default or Simple Tabs no debugging checks are raised.

So to me is enough to change my old settings from Firefox 2 to default to get a working default.conf (my old one). I hope this helps to understand how to fix the issue.

[luisalberto]

Goto to Settings -> Environments Select Colours and over the OK and Cancel Buttons You will see the combo Box to change the theme. I am using Windows 11 25 H2. See the attach Image file. I dont like the dark mode and I use Light mode in Codeblocks.

[gd_on]

Effectively, I forgot to mention this as a third solution, introduced quite recently.
Nevertheless, the 2nd solution may be applied to many wxwidgets softwares where darkmode is not explicitely implemented. 

[20k]

[Main Instruction]
A debugging check in this application has failed.

I've found that deleting the .conf file just one time solved this for me.

Pecan, trying to re-customize my default.conf I think I found the root cause of the issue and so a quick way to fix it. The root cause of the debugging checks is a specific setting

Settings->Environment Settings->Notebooks Appearance->Tab Style

If you set the tab style to Firefox2 or Microsoft Visual Studio 7.1 the debugging checks are raised

Uisng default or Simple Tabs no debugging checks are raised.

So to me is enough to change my old settings from Firefox 2 to default to get a working default.conf (my old one). I hope this helps to understand how to fix the issue.

This didn't work for me (I'm experiencing the same problem), as my tabs were set to default already

[eckard_klotz]

Hello Developers.

Unfortunately the folding margin is located next to the text inside the editor and thus, it happens very easily that you force a folding even you just want click at the first line position, what is very annoying.

While reviewing the current margin configuration in cbEditor.cpp, I noticed that Code::Blocks defines its own margin IDs:

Code

#define C_LINE_MARGIN      0
#define C_MARKER_MARGIN    1
#define C_CHANGEBAR_MARGIN 2
#define C_FOLDING_MARGIN   3

As far as I understand it, Scintilla (and wxScintilla) always render margins strictly in ascending ID order.
Because of this, the folding margin (ID 3) appears directly next to the text area in the editor. This placement makes it easy to accidentally trigger fold/unfold actions when clicking near column 1, especially on high‑resolution displays.

Other Scintilla‑based editors (SciTE, Geany, Notepad++) avoid this issue by placing the folding margin immediately to the right of the line‑number margin. This provides a natural buffer zone and significantly reduces accidental folding.

In Code::Blocks, the folding margin is configured here:

Code

control->SetMarginType(C_FOLDING_MARGIN, wxSCI_MARGIN_SYMBOL);
control->SetMarginWidth(C_FOLDING_MARGIN, foldingMarginBaseWidth);
control->SetMarginMask(C_FOLDING_MARGIN, ...);
control->SetMarginSensitive(C_FOLDING_MARGIN, 1);

Since all margin‑related logic consistently seems to use the symbolic constants (C_FOLDING_MARGIN, C_MARKER_MARGIN, etc.), adjusting the margin order is limited to changing the four #define values. No other code changes should be required, and no plugins or configuration files are affected.

Suggested improvement: 
Reassign the folding margin to a lower ID (e.g., 1), so the margin order becomes:

Line numbers → Folding → Marker → Changebar → Text


This can simply be changed while the definition of the preprocessor constants like this:

Code

#define C_LINE_MARGIN      0
#define C_FOLDING_MARGIN   1
#define C_MARKER_MARGIN    2
#define C_CHANGEBAR_MARGIN 3

I think this small, isolated change would align Code::Blocks with common Scintilla practice and improve usability without introducing new settings or breaking existing functionality.


Please take a look to this and thank you in advance.

Best regards,
                   Eckard Klotz.