Recent Posts

1

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

« Last post by ollydbg on Today at 01:45:21 pm »

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

Well. A patch file or a diff file can be obtained by some version control tool. For example, svn or git. For C::B source, it has svn code repo, and git code mirrors. You can fetch the code from svn code repo or clone the code from git repo, and make some modification to the source code, and later generate patch file.

2

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

« Last post by bezet on Today at 10:16:46 am »

Hi, thanks to both for your replies. I'm afraid I can't reproduce the error !?

1) Here is what I did:
- create new Project -> wxWidgets project
(then I added a few components to the main Frame1)
- add a second frame using menu wxSmith -> Add wxFrame
-> second Frame2 which is a child of the first
(I added a few components to Frame2, among them a MathPlot which gives some heartache)
...then I noticed that Frame2 is destroyed when I close it, but I only want to hide it, so it can be reopened
-> I tried to create an event OnClose (using the Component Properties/Events window) , in order to overwrite with a 'simple' Hide()
...but this results in the error "cannot create event", same for components inside Frame2,
but everything is fine for Frame1,
and for a third frame which I created same way as Frame2 !
 
2) reproducing the error:
I have deleted the misbehaving Frame2,
but I found and reinstalled an old version of my program (saved 10 days ago), with Frame2 and Mathplot in it: the problem has disappeared !?

3) submenu "Configure wxSmith for current project"
nothing special inside, I made no changes:
- "automatically loaded ressources" is empty,
- Main resource = Frame1,
- "callwxXmlResource" is ticked
- "'only when necessary' is ticked

Thanks again, and in advance, for any hints!

3

Using Code::Blocks / Re: Lexer for C only?

« Last post by christo on Yesterday at 07:05:26 pm »

Attaching patch
1.  new lexer for C language - duplicated C++ lexer, removed c++ keywords and add more C keywords.
2. .c files uses the new lexer by default.
3. .h files uses C++ lexer if C++ files are present in the project,  else uses the new C lexer

4

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

« Last post by LR83 on Yesterday 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?

5

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

« Last post by ollydbg on Yesterday 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.

6

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

« Last post by LR83 on March 28, 2026, 02:57:59 pm »

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

7

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.

8

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.

9

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!?

10

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.