Recent Posts

41

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.

42

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());
        }

43

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? 

44

Development / Re: wxSmith use bad constructor for wxStaticBoxSizer

« Last post by Miguel Gimenez on January 12, 2026, 03:59:40 pm »

Fixed in r13767.

45

Help / Re: Incremental Search text box selects itself

« Last post by Miguel Gimenez on January 10, 2026, 02:16:22 pm »

Fixed on Ubuntu, should work also on Debian (commit 13764).

46

Help / Re: Incremental Search text box selects itself

« Last post by Miguel Gimenez on January 10, 2026, 01:45:27 pm »

If you can compile C::B you can try changing this code (in IncrementalSearch.cpp)

Code

#ifdef __WXMAC__
    // on macOS only set focus if we really lost it, to avoid native select all,
    // or it will reset the text selection
    if (!m_pTextCtrl->HasFocus())
        m_pTextCtrl->SetFocus();
#else
    m_pTextCtrl->SetFocus();
#endif

to just

Code

    // only set focus if we really lost it, to avoid native select all
    // or it will reset the text selection
    if (!m_pTextCtrl->HasFocus())
        m_pTextCtrl->SetFocus();

47

Help / Re: Incremental Search text box selects itself

« Last post by sedenion on January 10, 2026, 11:35:49 am »

Hi,

This issue still here in Debian 13 (LMDE 7) Is it an Incremental Search plugin problem or related to WxSmith ? It seem pretty odd that this problem still not addressed since 2022...

48

Development / Re: wxSmith use bad constructor for wxStaticBoxSizer

« Last post by LR83 on January 09, 2026, 10:51:16 am »

The main difficulty lies in the fact that wxStaticBoxSizer is both a sizer and a container. In the current code, wxStaticBoxSizer is classified as a sizer, and there is no category for an object that is both a sizer and a container.
The difficulty lies in finding the owner of the child elements of wxStaticBoxSizer. Currently, it is the parent of the wxStaticBoxSizer that is found, and that is the problem.
The problem is clear, the solution less so!
We will probably need to create a new category and the wxsStaticBoxSizer class will need to inherit from wxsSizer and wxsContainer 

49

Development / Re: wxSmith use bad constructor for wxStaticBoxSizer

« Last post by Miguel Gimenez on January 09, 2026, 08:50:49 am »

wxSmith is complex and the original developer is no longer around. I plan to fix this, but I currently have no free time.

50

Using Code::Blocks / Re: debugger plugin's tip windows does not show content with horizontal scroll bar

« Last post by Pecan on January 09, 2026, 03:29:12 am »

Not the debug tip window, sometimes, the code completion tip(from the clangd_client plugin) window becomes extremely large, see the blow two screen shot, the tip window cover the whole C::B window, also the tip window extended to another screen. 

""
In settings>editor>CodeCompletion what have you got set for "Maximum allowed code completion matches" ?

Hi, sorry for the late reply.
I just looked at my settings, and I see the value is 1000. Is that too big?

I'd say 1000 responses is enough to over fill your screen. 20 to 40 on the screen should be adequate.