Recent Posts

1

Help / Re: code::blocks hangs at startup

« Last post by Miguel Gimenez on Today at 01:44:53 pm »

On 2.43 gdk-pixbuf deprecated the XPM api and disabled XPM loader by default, see release notes.

wxSmith defines a XPM in wxSmith.cpp:50 and uses it during plugin attachment in wxSmith.cpp:211; Probably changing this XPM to a PNG or SVG fixes the issue.

2

Help / Re: code::blocks hangs at startup

« Last post by Miguel Gimenez on Today at 11:44:33 am »

Works OK on Ubuntu 22.04 with wxWidgets 3.2.6, I cannot check on other Linux. wxSmith uses some initialization tricks that may be non-portable.

This ticket reports that downgrading gdk-pixbuf2 from 2.44.2-1 to 2.42.12-2 fixes the problem.

3

Help / Re: code::blocks hangs at startup

« Last post by stahta01 on Today at 11:36:16 am »

2 days ago, since a very long time, I did a fresh build of CB on linux, in Tumbleweed.
Build goes fine, but launching fails. With a similar problem as mentioned above, and the 'renaming' the 3 wxSmith zip files.
Probably when starting a build by excluding these plug-in(s) things would have been ok too.

Code

sudo mv /usr/local/share/codeblocks/wxSmithAui.zip /usr/local/share/codeblocks/wxSmithAui.old
sudo mv /usr/local/share/codeblocks/wxsmithcontribitems.zip /usr/local/share/codeblocks/wxsmithcontribitems.old
sudo mv /usr/local/share/codeblocks/wxsmith.zip /usr/local/share/codeblocks/wxsmith.old

Conclusion: this problem is not solved yet, did anyone in the meantime had a look at it ?



for reference, I stumbled also upon: https://bbs.archlinux.org/viewtopic.php?id=308575

What wxWidget version is being used?
My wild guess is the png images; I checked one image file and if not wxCHECK_VERSION(3, 1, 6) then png images are used.
Edit: The single source file (wxsitemeditor.cpp) I checked was the only one that used the svg images if 3.1.6 or newer.

Tim S.

4

Help / Re: code::blocks hangs at startup

« Last post by killerbot on Today at 09:58:26 am »

2 days ago, since a very long time, I did a fresh build of CB on linux, in Tumbleweed.
Build goes fine, but launching fails. With a similar problem as mentioned above, and the 'renaming' the 3 wxSmith zip files.
Probably when starting a build by excluding these plug-in(s) things would have been ok too.

Code

sudo mv /usr/local/share/codeblocks/wxSmithAui.zip /usr/local/share/codeblocks/wxSmithAui.old
sudo mv /usr/local/share/codeblocks/wxsmithcontribitems.zip /usr/local/share/codeblocks/wxsmithcontribitems.old
sudo mv /usr/local/share/codeblocks/wxsmith.zip /usr/local/share/codeblocks/wxsmith.old

Conclusion: this problem is not solved yet, did anyone in the meantime had a look at it ?



for reference, I stumbled also upon: https://bbs.archlinux.org/viewtopic.php?id=308575

5

Development / Re: unified workspace and cbp under Windows for different wxWidgets versions

« Last post by Miguel Gimenez on Yesterday at 09:33:03 am »

Future spam added to radar.

6

Development / Re: unified workspace and cbp under Windows for different wxWidgets versions

« Last post by Larrying on Yesterday at 04:12:50 am »

This approach seems like a step in the right direction. A unified workspace would definitely streamline the development process, especially for handling different wxWidgets versions under Windows.

7

Using Code::Blocks / Re: Input / output redirection before run

« Last post by vici on January 19, 2026, 07:43:13 am »

Project -- Set program's argument -- Select your target -- Program arguments

Your solution passes the string "<input.txt" to argv[0], so in the program, one needs to use fopen, fget... And that string as argument to fscaf() will fail, because of the redirection character at the beginning.

OP (and me as well) want to use only scanf to read the data, and not care about the file name.

Problem still unanswered, using Codeblocks 25.03 under Windows 10.

8

Development / Re: wxSmith use bad constructor for wxStaticBoxSizer

« Last post by Bug Killer on January 17, 2026, 11:08:39 am »

Fixed in r13767.

Works fine on AlmaLinux 9 with wxWidgets 3.3.1. Don't forget to modify slightly all the dialogs, frames and panels. I just add a space somewhere and remove it.

9

Development / Re: wxSmith use bad constructor for wxStaticBoxSizer

« Last post by LR83 on January 13, 2026, 05:38:33 pm »

Great, work fine 
But I suggest using a temporary variable because wxStaticBoxSizer can have many children.
So, code could be:
In wxStaticBoxSizer.cpp:

Code

        case wxsCPP:
        {
            AddHeader(_T("<wx/sizer.h>"),GetInfo().ClassName,hfInPCH);
            AddHeader(_T("<wx/statbox.h>"),GetInfo().ClassName,hfInPCH);
            Codef(_T("%C(%s, %W, %t);\n"),
                    (Orient == wxHORIZONTAL) ? _T("wxHORIZONTAL") : _T("wxVERTICAL"),
                    Label.wx_str());
            Codef(_T("wxStaticBox *SB_%s = %s->GetStaticBox();\n"),GetVarName().wx_str(),GetVarName().wx_str());
            return;
        }

in wxSizer.cpp:

Code

        if (GetInfo().ClassName == "wxStaticBoxSizer")
        {
            // Use the static box as parent, as required by wxWidgets since 2.9.1
            wxsCoderContext* context = GetCoderContext();
            const wxString saveParent(context->m_WindowParent);
            context->m_WindowParent = "SB_" + GetVarName();
            Child->BuildCode(context);
            context->m_WindowParent = saveParent;
        }
        else
        {
            // Using same parent as we got, sizer is not a parent window
            Child->BuildCode(GetCoderContext());
        }

10

General (but related to Code::Blocks) / Re: Welcome Newcomers - PLEASE READ!!!

« Last post by MokpotheMighty on January 13, 2026, 04:21:59 pm »

Yeah, it's me, Im here and I'm new.

Speaking of, I'm trying to reply to my own thread with more info about the issue I ran into, but it's not letting me for some reason.

So I'm kind of posting here as a test to see if I can't post on this forum at all, or just here.

By the way, the anti spam filter still considers the last year to be 2024?