Recent Posts

71

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...

72

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 

73

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.

74

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.

75

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

« Last post by ollydbg on January 08, 2026, 12:11:19 pm »

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?

76

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

« Last post by Pecan on January 07, 2026, 10:34:40 pm »

Scroll bar overlaying problem fixed in rev 13763.
wxPropertyGrid assert fixed in the same rev.

I cannot reproduce the CodeCompletion huge tip size since my
 Settings>Editor>CodeCompletion setting for "Maximum allowed code completion matches" is a reasonable size.

77

General (but related to Code::Blocks) / Re: C::B reports wxRecursionGuards error when loading a cbp project

« Last post by Pecan on January 07, 2026, 10:32:35 pm »

I can reproduce the error with wx 3.3.2 on Linux.

The analysers scan-build or cppcheck show several issues with Clangd_client.

Would you care to share those issues with us?
Can you tell us how to reproduce the issue?

78

Development / Re: wxSmith use bad constructor for wxStaticBoxSizer

« Last post by LR83 on January 07, 2026, 06:14:31 pm »

I try to find a patch to correct this.
First, we can add a temporary wxStaticBox when we add the wxStaticBoxSizer.
In the file wxsstaticboxsizer.cpp we replace in OnBuildSizerCreatingCode() function this 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("wxVERTICAL"):_T("wxHORIZONTAL"),
                    Label.wx_str());
            Codef(_T("wxStaticBox *SB_%s = %s->GetStaticBox();\n"),GetVarName().wx_str(),GetVarName().wx_str());
            return;
        }

The problem now is to replace, in all constructors of the children of wxStaticBoxSizer, the parent with this temporary wxStaticBox.
I don't know how to do it right now.

79

Development / Re: wxSmith use bad constructor for wxStaticBoxSizer

« Last post by LR83 on January 07, 2026, 11:42:32 am »

We can correct the code simply by:
- replace this by StaticBoxSizer1->GetStaticBox() in the wxStaticText and wxTextCtrl constructor
- add the include <wx/statbox.h>

80

Development / wxSmith use bad constructor for wxStaticBoxSizer

« Last post by LR83 on January 07, 2026, 11:17:45 am »

The documentation say that the child of a wxStaticBoxSizer should be the wxBoxSizer and not the owner of the wxStaticBoxSizer.
On Linux, for example, I can see the following warning on the console:
Element wxStaticText of wxStaticBoxSizer should be created as child of its wxStaticBox and not of wxDialog.

I test several builder on a very simple case: a dialog window with a wxStaticBoxSizer that contain a wxStaticText and a wxTextCtrl.
With wxSmith:

DialogFormSmith::DialogFormSmith(wxWindow* parent,wxWindowID id)
{
    //(*Initialize(DialogFormSmith)
    wxStaticBoxSizer* StaticBoxSizer1;

    Create(parent, id, _("Test with wxSmith"), wxDefaultPosition, wxDefaultSize, wxDEFAULT_DIALOG_STYLE, _T("id"));
    StaticBoxSizer1 = new wxStaticBoxSizer(wxHORIZONTAL, this, _("StaticBoxSizer"));
    StaticText1 = new wxStaticText(this, wxID_ANY, _("Label"), wxDefaultPosition, wxDefaultSize, 0);
    StaticBoxSizer1->Add(StaticText1, 1, wxALL|wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL, 5);
    TextCtrl1 = new wxTextCtrl(this, wxID_ANY, _("Text"), wxDefaultPosition, wxDefaultSize, 0, wxDefaultValidator);
    StaticBoxSizer1->Add(TextCtrl1, 1, wxALL|wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL, 5);
    SetSizer(StaticBoxSizer1);
    StaticBoxSizer1->SetSizeHints(this);
    //*)
}

with wxFormBuilder:

DialogFormBuilder::DialogFormBuilder( wxWindow* parent, wxWindowID id, const wxString& title, const wxPoint& pos, const wxSize& size, long style ) : wxDialog( parent, id, title, pos, size, style )
{
   this->SetSizeHints( wxDefaultSize, wxDefaultSize );

   wxStaticBoxSizer* sbSizer1;
   sbSizer1 = new wxStaticBoxSizer( new wxStaticBox( this, wxID_ANY, _("StaticBoxSizer") ), wxHORIZONTAL );

   m_staticText1 = new wxStaticText( sbSizer1->GetStaticBox(), wxID_ANY, _("MyLabel"), wxDefaultPosition, wxDefaultSize, 0 );
   m_staticText1->Wrap( -1 );
   sbSizer1->Add( m_staticText1, 0, wxALL, 5 );

   m_textCtrl1 = new wxTextCtrl( sbSizer1->GetStaticBox(), wxID_ANY, wxEmptyString, wxDefaultPosition, wxDefaultSize, 0 );
   sbSizer1->Add( m_textCtrl1, 0, wxALL, 5 );


   this->SetSizer( sbSizer1 );
   this->Layout();
   sbSizer1->Fit( this );

   this->Centre( wxBOTH );
}

With wxGlade:

DialogFormGlade::DialogFormGlade(wxWindow* parent, wxWindowID id, const wxString& title, const wxPoint& pos, const wxSize& size, long style):
    wxDialog(parent, id, title, pos, size, wxDEFAULT_DIALOG_STYLE)
{
    // begin wxGlade: DialogFormGlade::DialogFormGlade
    SetTitle(wxT("Test with wxGlade"));
    wxStaticBoxSizer* sizer_1 = new wxStaticBoxSizer(new wxStaticBox(this, wxID_ANY, wxT("StaticBoxSizer")), wxHORIZONTAL);
    wxStaticText* label_1 = new wxStaticText(sizer_1->GetStaticBox(), wxID_ANY, wxT("Label"));
    sizer_1->Add(label_1, 0, 0, 0);
    text_ctrl_1 = new wxTextCtrl(sizer_1->GetStaticBox(), wxID_ANY, wxEmptyString);
    sizer_1->Add(text_ctrl_1, 0, 0, 0);

    SetSizer(sizer_1);
    sizer_1->Fit(this);
    Layout();
    // end wxGlade
}

The codes generated by wxFormBuilder and wxGlade are good: no warning.
I join a complete project for testing