Recent Posts

51

General (but related to Code::Blocks) / Re: New wxWidgets releases

« Last post by ollydbg on March 04, 2026, 06:31:35 am »

I just compare the 2 release:

https://github.com/wxWidgets/wxWidgets/compare/v3.3.1...v3.3.2

I see this that the only 2 functions were added in the file: include/wx/dynarray.h

Code

T& operator[](size_t uiIndex)
    {
        wxASSERT( uiIndex < this->size() );
        return base_vec::operator[](uiIndex);
    }

    const T& operator[](size_t uiIndex) const
    {
        wxASSERT( uiIndex < this->size() );
        return base_vec::operator[](uiIndex);
    }

52

General (but related to Code::Blocks) / Re: New wxWidgets releases

« Last post by ollydbg on March 04, 2026, 04:32:18 am »

Code

[ 23.3%] g++.exe -Wall -g -pipe -mthreads -fmessage-length=0 -fexceptions -DHAVE_W32API_H -D__WXMSW__ -D_WIN64 -DWXUSINGDLL -DcbDEBUG -DNOPCH -DBUILDING_PLUGIN -DwxUSE_UNICODE -std=gnu++11 -g -std=gnu++11 -IF:\code\wxWidgets-3.3.2\lib\gcc_dll\mswud -IF:\code\wxWidgets-3.3.2\include -I..\..\..\include -I..\..\..\include\tinyxml -I..\..\..\sdk\wxscintilla\include -I..\..\..\include\scripting\include -c F:\code\codeblocks-src\codeblocks_sfmirror\src\plugins\contrib\wxSmith\wxwidgets\defitems\wxschoice.cpp -o ..\..\..\.objs33_64\plugins\contrib\wxSmithLib\wxwidgets\defitems\wxschoice.o
In file included from F:\code\wxWidgets-3.3.2\include/wx/arrstr.h:15,
                 from F:\code\wxWidgets-3.3.2\include/wx/ctrlsub.h:17,
                 from F:\code\wxWidgets-3.3.2\include/wx/listbox.h:21,
                 from F:\code\wxWidgets-3.3.2\include/wx/checklst.h:17,
                 from F:\code\codeblocks-src\codeblocks_sfmirror\src\plugins\contrib\wxSmith\wxwidgets\defitems\wxschecklistbox.cpp:24:
F:\code\wxWidgets-3.3.2\include/wx/dynarray.h: In instantiation of 'T& wxBaseArray<T, Sorter>::operator[](size_t) [with T = bool; Sorter = wxSortedArray_SortFunction<bool>; size_t = long long unsigned int]':
F:\code\codeblocks-src\codeblocks_sfmirror\src\plugins\contrib\wxSmith\wxwidgets\defitems\wxschecklistbox.cpp:72:35:   required from here
   72 |                 if ( ArrayChecks[i] )
      |                                   ^
F:\code\wxWidgets-3.3.2\include/wx/dynarray.h:128:36: error: cannot bind non-const lvalue reference of type 'bool&' to an rvalue of type 'bool'
  128 |         return base_vec::operator[](uiIndex);
      |                ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~
In file included from D:/code/msys2/mingw64/include/c++/14.2.0/vector:67,
                 from F:\code\wxWidgets-3.3.2\include/wx/strvararg.h:34,
                 from F:\code\wxWidgets-3.3.2\include/wx/string.h:34,
                 from F:\code\wxWidgets-3.3.2\include/wx/arrstr.h:14:
D:/code/msys2/mingw64/include/c++/14.2.0/bits/stl_bvector.h:99:5: note:   after user-defined conversion: 'std::_Bit_reference::operator bool() const'
   99 |     operator bool() const _GLIBCXX_NOEXCEPT
      |     ^~~~~~~~
Process terminated with status 1 (15 minute(s), 30 second(s))
 
Process terminated with status 0 (15 minute(s), 32 second(s))
1 error(s), 28 warning(s) (15 minute(s), 32 second(s))
 

I just tried, and I see the build failure as above.

I built the wx 3.3.2 library with the command:

Code

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=debug UNICODE=1

53

General (but related to Code::Blocks) / Re: New wxWidgets releases

« Last post by stahta01 on March 04, 2026, 01:11:32 am »

Has anyone gotten Code::Blocks to build with wx3.3.2?
I gave up building wxWidgets git master about a month ago because of a build error already reported on this website by someone else.
Had to do with scripting and the red, blue, and green methods.

Tim S.

54

General (but related to Code::Blocks) / Re: Display resolution issue

« Last post by JoeH on March 04, 2026, 12:35:45 am »

That is exactly what happened.  I tried to post a screen shot of the Help/About data, but I guess the image was too large.  I then passed it through an OCR program and missed correcting those two I's to ones.

I am currently chasing Miguel's leads on From and ToDPI but have not stumbled on anything promising yet.

I have given up on doing anything relative to the manifest because it is beyond my level of understanding.

Joe

55

General (but related to Code::Blocks) / New wxWidgets releases

« Last post by Miguel Gimenez on March 03, 2026, 06:55:10 pm »

wx3.2.10 and wx3.3.2 have been released simultaneously.

56

Using Code::Blocks / Line spacing in editor

« Last post by ron.dunn on March 03, 2026, 12:45:29 pm »

Is there a setting to increase the line spacing in the editor?

In Scintilla it should be possible with the following functions, but I can't find equivalent settings.

SCI_SETEXTRAASCENT(int extraAscent)
SCI_SETEXTRADESCENT(int extraDescent)

57

General (but related to Code::Blocks) / Re: Display resolution issue

« Last post by ollydbg on March 03, 2026, 01:59:10 am »

Maybe, the OP used some image shot and OCR software? 

58

General (but related to Code::Blocks) / Re: Display resolution issue

« Last post by Miguel Gimenez on March 02, 2026, 06:28:55 pm »

Windows 11 on laptops with a native resolution of 1920x1080 usually sets a 125 % scaling factor, so the PPI in logical pixels (DIP) may be 127/125 ~ 100. This scaling factor should appear in the About dialog, though.

One way to check your manifest (referring to your post on wxForums) is using Resource Hacker. This is part of the manifest from C::B

Code

<asmv3:application xmlns="urn:schemas-microsoft-com:asm.v1">
    <asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
      <dpiAware>True</dpiAware>
    </asmv3:windowsSettings>
</asmv3:application>

You can try using FromDIP() and ToDIP() from wxWindow.

EDIT: Strangely, your Windows version appears as "Windows II" (Windows 2 in roman numerals), not "Windows 11"; Did you edit the installation details?.

59

General (but related to Code::Blocks) / Display resolution issue

« Last post by JoeH on March 02, 2026, 03:07:10 pm »

   I am experiencing a difficulty with retrieving the dpi display value.  I want my program to draw to the display at actual size.  As an example, I want to draw a circle with a 3 inch diameter to the screen and when the display is measured with a ruler, the circle measures 3 inches in diameter.  I want to accomplish this without the user having to input any scaling information and regardless of the display resolution the user has implemented on his computer.

   Here are the details of my installation from the CodeBlocks Help/About display:

Name               : Code::Blocks
Version                     : 25.03-r13644
SDK Version            : 2.25.0
Scintilla Version                 : 3.7.5
Author               : The Code::Blocks Team
E-mail               : info@codeblocks.org
Website                    : https://www.codeblocks.org
OS                       : Windows ll (build 26100), 64-bit edition
Scaling factor            : 1.000000
Detected scaling factor      : 1.000000
Display PPI            : 96x96
Display count            : 1
Display 0 (\\.\DISPLAY1)      : XY=[0,0]; Size=[1920,1080]; Primary

wxWidgets Library (wxMSW port)
Version 3.2.7 (Unicode: wchar_t, debug level: 1),
compiled at Mar 25 2025 17:16:27

Runtime version of toolkit used is 10.0.26100.

I am using a HP laptop that has a display that is 15 inches wide and 8.5 inches high.  My calculator tells me that the PPI for 1920x1080 is 127 (close enough) in each direction.  As you can see above, the reported Display PPI is 96x96.  These are the values I get within my program as well.

   If I manually enter the 127 ppi into my program I get the display results I desire (actual size).  Is there a mechanism to get the actual ppi from a system call?

   Thanks for your help.

Joe

60

Development / Re: unified workspace and cbp under Windows for different wxWidgets versions

« Last post by Miguel Gimenez on March 02, 2026, 09:34:50 am »

BTW. I nener known that we(or some cb dev) can access the Fortran plugin snv repo.

Some of us can (see the commit log there), but usually we avoid the Fortran-specific part.