Recent Posts

71

Development / Re: svn rev 13798 issue?

« Last post by ollydbg on March 01, 2026, 02:24:51 am »

I have seen that inside ....\src\tools\test\macrosmanager there is a macrosmanager.cbp file. It can display variables in the C::B log window if you launch a build or full rebuild command. The display is a little bit heavy/confusing, but it exists!

Oh, yes, this is a command like project, I see there are a lot of command line statement when you "build"(actually you do no build the project, but just run the command) the project.

Code

					<Add before="echo Code::Blocks location: $(CODEBLOCKS)" />
					<Add before="echo Code::Blocks APP_PATH: $(APP_PATH)" />
					<Add before="echo Code::Blocks DATA_PATH: $(DATA_PATH)" />
					<Add before="echo Code::Blocks PLUGINS: $(PLUGINS)" />
					<Add before="echo Code::Blocks LANGUAGE: $(LANGUAGE)" />
					<Add before="echo Code::Blocks ENCODING: $(ENCODING)" />

PS: in some of the clangd_client_wx*.cbp, the $(CODEBLOCKS) variable is still used.

Let me fix them, I can find them by search the $(CODEBLOCKS) in all the *.cbp files.

72

Nightly builds / Re: The 09 February 2026 build (13785) is out.

« Last post by Miguel Gimenez on February 28, 2026, 12:08:22 pm »

Change applied in r13802, thank you.

73

Nightly builds / Re: The 09 February 2026 build (13785) is out.

« Last post by Miguel Gimenez on February 28, 2026, 11:15:57 am »

Thank you, I will integrate this.

74

Contributions to C::B / Re: Fixed project tree broken sort

« Last post by ollydbg on February 28, 2026, 03:26:31 am »

Thanks, I'm not familiar with this part of the code. Other devs may have a try. 

75

Contributions to C::B / Fixed project tree broken sort

« Last post by Hazanko on February 28, 2026, 02:49:01 am »

Project tree does not properly sort alpha when number of parents reaches a certain count(?). I'm assuming this has something to do with wx reallocating for more space and breaking the tree structure.
This is not an issue on my other machine with codeblocks 20.03/wxgtk3.05 handles sorting properly, as well as on windows(20.03,nightly,25.03).

Included checks for directories vs dirs & directories vs files in cbTreeCtrl::OnCompareItems(...).
Removed call to ProjectFindNodeToInsertAfter(...) in ProjectAddTreeNode(...) as sorting will be entirely handled by sorting children, as well as adding item as first child as we don't care about order at this point.

76

Nightly builds / Re: The 09 February 2026 build (13785) is out.

« Last post by Xaviou on February 27, 2026, 10:24:15 pm »

Hi

EDIT:
The solution recommended by Gemini is the same but using "unsigned int"

Code

BindMethod(v, _SC("GetAlpha"), NoParamGetterInt<unsigned int, wxColour, &wxColour::GetAlpha>, _SC("wxColour::GetAlpha"));

Well : I've also submitted the problem to an AI (Claude via the Codex extension of VSCode)  : it gave me a more complex solution (tested with rev 13793 and it worked) :

He told me to add 4 new functions (near other wrappers wxColour, for example, after wxColour_To_String) :

Code

SQInteger wxColour_Blue(HSQUIRRELVM v)
{
    ExtractParams1<const wxColour*> extractor(v);
    if (!extractor.Process("wxColour_Blue"))
        return extractor.ErrorMessage();
    sq_pushinteger(v, extractor.p0->Blue());
    return 1;
}

SQInteger wxColour_Green(HSQUIRRELVM v)
{
    ExtractParams1<const wxColour*> extractor(v);
    if (!extractor.Process("wxColour_Green"))
        return extractor.ErrorMessage();
    sq_pushinteger(v, extractor.p0->Green());
    return 1;
}

SQInteger wxColour_Red(HSQUIRRELVM v)
{
    ExtractParams1<const wxColour*> extractor(v);
    if (!extractor.Process("wxColour_Red"))
        return extractor.ErrorMessage();
    sq_pushinteger(v, extractor.p0->Red());
    return 1;
}

SQInteger wxColour_Alpha(HSQUIRRELVM v)
{
    ExtractParams1<const wxColour*> extractor(v);
    if (!extractor.Process("wxColour_Alpha"))
        return extractor.ErrorMessage();
    sq_pushinteger(v, extractor.p0->Alpha());
    return 1;
}

And then, replacing the 4 "BindMethod" witch were causing the build error:

Code

BindMethod(v, _SC("Blue"), wxColour_Blue, _SC("wxColour::Blue"));
BindMethod(v, _SC("Green"), wxColour_Green, _SC("wxColour::Green"));
BindMethod(v, _SC("Red"), wxColour_Red, _SC("wxColour::Red"));
BindMethod(v, _SC("Alpha"), wxColour_Alpha, _SC("wxColour::Alpha"));

Regards
Xav'

77

Nightly builds / Re: The 26 February 2026 build (13800) is out.

« Last post by Xaviou on February 27, 2026, 10:10:49 pm »

Hi.

32 bits version for Windows (and also 64 bits version) can be downloaded from my website.
I made both a wxWidgets-3.2.8 and wxWidgets-3.3.1 linked versions

Debian Trixie (64 bits) and Bookworm (32 and 64 bits) can be installed from my repo
The corresponding unsigned deb files can also be downloaded from the website page linked above.

Ubuntu-22.04, 24.10 and 25.10 versions can be installed from my ppa (they are now available for both amd64 and arm64 architectures).

Regards
Xav'

78

Development / Re: svn rev 13798 issue?

« Last post by gd_on on February 27, 2026, 09:39:24 am »

I have seen that inside ....\src\tools\test\macrosmanager there is a macrosmanager.cbp file. It can display variables in the C::B log window if you launch a build or full rebuild command. The display is a little bit heavy/confusing, but it exists!

PS: in some of the clangd_client_wx*.cbp, the $(CODEBLOCKS) variable is still used.

79

Development / Re: svn rev 13798 issue?

« Last post by ollydbg on February 27, 2026, 01:08:51 am »

I've reverted the use of built-in variables in the codesnippets.cbp.

Sadly, this means we can never  use the built-in macros in a .cbp file.

Hello pecan, thanks for the fix.

I think basically linking the recent built plugin to the host CB has another issue. Sometimes
the host CB and the client CB have different SDK numbers, I'm just avoid doing that.

About print the Macro values,  Maybe we can have a Squirrel script to print all those values.

80

Development / Re: svn rev 13798 issue?

« Last post by Pecan on February 26, 2026, 08:05:01 pm »

Is there a way to display within Code::Blocks the content of environment variables that are set by MacrosManager, so AMP, CODEBLOCKS, APP_PATH, ...

Would displaying the built-in vars within Code::Blocks allow us to use them in .cbp files?
Would that avoid the problems experienced by ollydbg?