Recent Posts

1

Development / Re: wxSmith : add option for Create function in inhereited cases

« Last post by LR83 on Today at 09:20:07 am »

Yes, the change is very slight and does not disrupt normal behavior.
We now just have a new option to call or not the Create() function (the default value is true in order to keep the old generation code).
I introduced this because when you call the parent in the constructor, you should not use the Create() function.

I don't know how to create a "patch file". Do I need a special environment?

2

Development / Re: wxSmith : add option for Create function in inhereited cases

« Last post by ollydbg on Today at 12:22:50 am »

Is my proposition posted above on January 24, 2026 work for everybody and could be added on next release ?

So, you want an option to enable/disable the usage of "Create" function? Sorry I'm still not quite understand your idea, and I'm not quite familiar with wxSmith's source code.

I just copy your code in the attachment to the local code repo, and I see it does not change much. And can you modify your code to a patch file, which is against the last code base?

I hope some devs who are more familiar with wxSmith will review your patch file.

3

Development / Re: wxSmith : add option for Create function in inhereited cases

« Last post by LR83 on Yesterday at 02:57:59 pm »

Is my proposition posted above on January 24, 2026 work for everybody and could be added on next release ?

4

General (but related to Code::Blocks) / Re: wxSmith Couldn't Add New Handler

« Last post by Miguel Gimenez on March 27, 2026, 07:41:07 pm »

There are only two possible causes of this error:
- There is no // (*Handlers(FrameName) section in the dialog's include file
- An editor for the source file cannot be opened

See wxsEventsEditor::CreateNewFunction() for more information.

In the wxSmith menu there is a submenu (Configure wxSmith for current project) that may help

I would bet for an invalid file name.

5

General (but related to Code::Blocks) / Re: wxSmith Couldn't Add New Handler

« Last post by ollydbg on March 27, 2026, 04:19:53 pm »

Can you show us a step by step instructions? We need to reproduce this bug in our C::B. Unluckily, I don't know the steps.

6

General (but related to Code::Blocks) / Re: wxSmith Couldn't Add New Handler

« Last post by bezet on March 27, 2026, 02:06:56 pm »

Hello, I confirm that the same problem persists in March 2026 :
After adding a child window/frame using the wxSmith menu 'New Frame', I was unable to create/add any events.
Also components added to this frame return the same error "Couldn't Add New Handler" .
I looked at thevarious files to find any wrong path etc., without success.
Then I created another child frame in the same way, and there is no problem to create events!?

7

Development / Re: flicker when I rezize the Build log control(TextCtrlLogger) issue

« Last post by ollydbg on March 26, 2026, 01:38:18 pm »

 I wrote some code snippet like this

Code

    if (control)
    {
        // Check if it's already enabled (either by default or previously set)
        if (!control->IsDoubleBuffered())
        {
            control->SetDoubleBuffered(true);
        }

        // Always a good idea to bind this if you're still seeing "white flashes"
        control->Bind(wxEVT_ERASE_BACKGROUND, [](wxEraseEvent& event) {
            // Leave empty to prevent background clearing
        });
    }

I set the breakpoint inside the "if (!control->IsDoubleBuffered())" clause, and I see it hit there. So, under wx 3.3.2, the double buffer is not enabled by default, so calling the "control->SetDoubleBuffered(true);" will enable it.

in fact, it is not redrawn until I release the mouse button

OK, I see such option, it is an option for Windows OS's graphics system to reduce the flicker.

8

Development / Re: flicker when I rezize the Build log control(TextCtrlLogger) issue

« Last post by Miguel Gimenez on March 25, 2026, 04:17:58 pm »

So, the double buffering is disabled by default in 3.3.2 for the wxTextCtrl class?

I do not know, try calling control->IsDoubleBuffered() after loggers.cpp:171. With 3.2.10 it returns false, and the control does not flicker (in fact, it is not redrawn until I release the mouse button).

9

Nightly builds / Re: The 24 March 2026 build (13828) is out.

« Last post by killerbot on March 25, 2026, 03:59:32 pm »

was on the todo list:
* wx 3.3.2
* gcc 15.2

I think will do the wx step up first.

10

Development / Re: flicker when I rezize the Build log control(TextCtrlLogger) issue

« Last post by ollydbg on March 25, 2026, 03:07:10 pm »

Which version of wxWidgets are you using?

I'm using the latest wx 3.3.2 release.

Double buffering behaviour has been modified around wx3.3.2, see for example Revert "Enable double buffering for all generic windows in wxMSW"

So, the double buffering is disabled by default in 3.3.2 for the wxTextCtrl class?