Recent Posts

1

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

« Last post by Miguel Gimenez on Yesterday at 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.

2

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

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

3

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

« Last post by bezet on Yesterday at 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!?

4

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.

5

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

6

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.

7

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?

8

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

« Last post by Miguel Gimenez on March 25, 2026, 02:03:27 pm »

Which version of wxWidgets are you using?

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

9

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

« Last post by ollydbg on March 25, 2026, 01:25:22 pm »

Hi, thanks, I see it still uses wx 3.2.8.

Maybe, you could try a more recent wxWidgets version, see here: wxWidgets 3.2.10 and 3.3.2 Released - wxWidgets

BTW: I use the github action to build a wx 3.3.2 based version(since Tim has made contribution to the msys2's wx package, thanks).
See:
asmwarrior/x86-codeblocks-builds: Automatically built codeblocks for both 32b and 64b Windows systems.

and my forked C::B source of a git mirror:

asmwarrior/codeblocks_sfmirror: Unofficial auto-updated GIT mirror of C::B repo in SourceForge. Does NOT accept patches nor pull requests.

10

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

« Last post by ollydbg on March 25, 2026, 01:20:21 pm »

Today, I noticed that when I resize the "Build log" panel, I see this window get flickered a lot. When I drag the panel edge between our cbEditor window and the Build log, I don't see the cbEditor get flickered.

So, I prepared a patch, and it looks like with this patch, the "Build log"'s flicker get reduced, can you try this patch? Or maybe there are many other method to handle this.

Code

From 015270b1dc35f3020e549c0e7af310fcb682b66d Mon Sep 17 00:00:00 2001
From: asmwarrior <hidehide@hidehide.com>
Date: Wed, 25 Mar 2026 18:08:38 +0800
Subject: [PATCH] text logger: try to enable the double buffering to stop the
 flickering

---
 src/sdk/loggers.cpp | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/src/sdk/loggers.cpp b/src/sdk/loggers.cpp
index f3ec29f8d..25f8d5c18 100644
--- a/src/sdk/loggers.cpp
+++ b/src/sdk/loggers.cpp
@@ -169,6 +169,17 @@ wxWindow* TextCtrlLogger::CreateControl(wxWindow* parent)
 {
     if (!control)
         control = new wxTextCtrl(parent, -1, wxEmptyString, wxDefaultPosition, wxDefaultSize, wxTE_MULTILINE | wxTE_READONLY | wxTE_RICH | wxTE_NOHIDESEL | wxTE_AUTO_URL);
+
+    // Enable double buffering to stop flickering
+    if (control)
+    {
+        control->SetDoubleBuffered(true);
+        // In your event table or Bind calls:
+        control->Bind(wxEVT_ERASE_BACKGROUND, [](wxEraseEvent& event) {
+            // Do nothing here to skip the default background clearing
+        });
+    }
+
     return control;
 }
 

Thanks.