Author Topic: The 08 October 2022 build (12969) is out.  (Read 4973 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5387
The 08 October 2022 build (12969) is out.
« on: October 08, 2022, 05:16:58 pm »
We switched to wx 3.2.1 (on 01 October 2022) --> download the new wx dll's see link below

Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works.

A link to the unicode windows wxWidget dll(s) for Code::Blocks : https://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw32u_gcc_cb_wx321_2D_gcc810-mingw64.7z
A link to Mingw64 dll's needed by Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls8.1.0.7z


The 08 October 2022 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2022/CB_20221008_rev12969_win64.7z
  - Linux :
   none

The current SDK version is : 2.22.0

Resolved Fixed:

  • IncrementralSearch: Fix HiDPI and use SVG.
  • Doxyblocks: Fix HiDPI with wxWidgets >= wx3.1.6.
  • Abbreviations: Use SVG icon.
  • Editor: Use SVG for breakpoint icons.
  • Use SVG in breakpoints dialog and as read-only marker in editor.
  • Use SVG icons in the project tree.
  • CompilerGCC: Add SVG files to autotools.
  • File options dialog: Do not change file read-only status if Cancel is pressed.
  • OpenFilesList: Use SVG with wxWidgets >= 3.1.6.
  • help_plugin: Use SVG with wxWidgets >= 3.1.6.
  • BrowseTracker: Use SVG with wxWidgets >= 3.1.6.
  • NassiShneiderman: Use SVG with wxWidgets >= 3.1.6.
  • Enable SVG from resource files (XRC).
  • CodeCompletion: Use SVG with wxWidgets >= 3.1.6.
  • CompilerGCC: Do not call Last() on an empty string.
  • SDK: Adapt cbArtProvider for using SVG.
  • Use SVG with cbArtProvider in the main window and some plugins.

Regressions/Confirmed/Annoying/Common bugs:



    Offline Xaviou

    • Regular
    • ***
    • Posts: 367
      • X@v's wxStuff
    Re: The 08 October 2022 build (12969) is out.
    « Reply #1 on: October 09, 2022, 12:51:01 am »
    Hi.

    OS X version of this rev can be downloaded from my Google Drive.
    There is only a macOS-11.6 version.
    Note that it is not a notarized version of the application.

    32 bits version for Windows can also be found in the same place (wx-3.1.7 with the aui patch).

    Debian Buster and Bullseye (32 and 64 bits) can be installed from my repo.

    Regards
    Xav'
    The french wxWidgets site : http://www.wxdev.fr
    My wxWidgets's stuff : https://wxstuff.xaviou.fr/

    Offline Pecan

    • Plugin developer
    • Lives here!
    • ****
    • Posts: 2530
    Re: The 08 October 2022 build (12969) is out.
    « Reply #2 on: October 09, 2022, 01:12:08 am »
    The Clangd_Client for this nightly can be downloaded at
    https://sourceforge.net/projects/cb-clangd-client/files/Plugin_Install_Package/Windows_x64/

    Filename: ClangdClientForCBNightly_20221008_rev12969_win64.zip (Direct download link)

    Copy the included clangd_client.zip to  <YourCodeBlocksNightlyFolder>\share\CodeBlocks\clangd_client.zip
    Do not unzip this file.

    Copy the included clangd_client.dll to <YourCodeBlocksNightlyFolder>\share\CodeBlocks\plugins\clangd_client.dll

    Restart your CodeBlocks Nightly.

    Install instructions for LLVM/clangd are included within the downloaded .zip file.
    « Last Edit: October 09, 2022, 02:11:04 am by Pecan »

    Offline MaxGaspa

    • Multiple posting newcomer
    • *
    • Posts: 25
    Re: The 08 October 2022 build (12969) is out.
    « Reply #3 on: October 09, 2022, 11:37:59 pm »
    Using the latest nightly I have a minor issue  using Win7 SP1 (Wian10 not yet tested). The icon for "search" and "replace" are identical.  Look at the attached images. Is that intentional?

    Offline Miguel Gimenez

    • Developer
    • Lives here!
    • *****
    • Posts: 1266
    Re: The 08 October 2022 build (12969) is out.
    « Reply #4 on: October 14, 2022, 07:06:21 pm »
    Fixed in [r12976], the 'R' was text and nanoSVG does not render text.

    Offline MaxGaspa

    • Multiple posting newcomer
    • *
    • Posts: 25
    Re: The 08 October 2022 build (12969) is out.
    « Reply #5 on: October 15, 2022, 03:45:51 pm »
    Using the latest nightly (and the latest Clangd plugin with the -2 suffix released by Pecan) and Win7 pro, I got the "black screen of death"  in the editor panel (fully black) and then a crash.

    Attached the related RPT file.

    Moreover why  are you still using DrMingw 0.9.1? It is a very old version, 0.9.7 is already available with impovements....
    « Last Edit: October 15, 2022, 03:50:05 pm by MaxGaspa »

    Offline ollydbg

    • Developer
    • Lives here!
    • *****
    • Posts: 5737
    • OpenCV and Robotics
      • Chinese OpenCV forum moderator
    Re: The 08 October 2022 build (12969) is out.
    « Reply #6 on: October 15, 2022, 04:52:59 pm »
    Using the latest nightly (and the latest Clangd plugin with the -2 suffix released by Pecan) and Win7 pro, I got the "black screen of death"  in the editor panel (fully black) and then a crash.

    Attached the related RPT file.

    Moreover why  are you still using DrMingw 0.9.1? It is a very old version, 0.9.7 is already available with impovements....

    DrMingw is now 0.9.8.

    See this post:

    Re: error alert message when using ThreadSearch Plugin

    Also, this issue:

    What is the minimal OS to run the official drmingw release?

    If you look at the reply of this issue, you will see that it will support Win7 but has many KBxxx installed:

    Quote
    It sounds the developer might be using a Windows 7 installation that lacks all updates from Microsoft.

    I'm afraid I can't afford chasing problems with out of date Windows 7 installations. I can't be sure that alone fixes the problem, but dealing with out of date Windows 7 installations presents too many unknowns, and there's no good reason to support it.

    I know updating Windows 7 can be tricky, as I recently experienced, because a Windows 7 freshly installed from an ISO is not able to automatically download updates from Microsoft, and one needs to follow the steps described here to bootstrap.

    But the above difficulties are not an excuse not to do it. It's imperative folks using Windows 7 do so, not only for better security, but also so we have all comparable systems.

    In short, to answer your question, the minimal OS to run drmingw releases is Windows 7 SP1, plus Platform Update, and all other updates from Microsoft Update. Anything older is unsupported.

    If the issue still reproduces after installing all Windows 7 updates, then let me know, and I'll look into it.
    If some piece of memory should be reused, turn them to variables (or const variables).
    If some piece of operations should be reused, turn them to functions.
    If they happened together, then turn them to classes.

    Offline MaxGaspa

    • Multiple posting newcomer
    • *
    • Posts: 25
    Re: The 08 October 2022 build (12969) is out.
    « Reply #7 on: October 15, 2022, 08:54:30 pm »
    DrMingw is now 0.9.8.

    Yes! I'm waiting a package update in Msys2. At the moment 0.9.7 is the latest available in Msys2


    If you look at the reply of this issue, you will see that it will support Win7 but has many KBxxx installed:

    I always used DrMingw from 0.8.x to 0.9.7 in both Win7 Pro (at home, always kept updated) and Win 10 Enterprise (at work) without any issue. May be because I have all the required updates.


    Anyway it seems that Msys2 is terminating the Win7 support by the end of the year, or early next year. Does CB keep the compatibility with Win7 in future?

    Offline Pecan

    • Plugin developer
    • Lives here!
    • ****
    • Posts: 2530
    Re: The 08 October 2022 build (12969) is out.
    « Reply #8 on: October 16, 2022, 01:04:14 am »
    Using the latest nightly (and the latest Clangd plugin with the -2 suffix released by Pecan) and Win7 pro, I got the "black screen of death"  in the editor panel (fully black) and then a crash.

    Attached the related RPT file.

    Moreover why  are you still using DrMingw 0.9.1? It is a very old version, 0.9.7 is already available with impovements....

    The codeblocks.rpt is not very helpful.
    It shows that wxWidgets did a program run (wxmsw32u_gcc_cb.dll!wxEventLoopBase::Run),
    which led to a windows paint which led to a wxScintilla paint which tried to get some Library info that ended up in codeblocks.dll reading from location 0.


    Offline killerbot

    • Administrator
    • Lives here!
    • *****
    • Posts: 5387
    Re: The 08 October 2022 build (12969) is out.
    « Reply #9 on: October 22, 2022, 09:48:25 am »
    something happening probably in later code (notiewd it while bulding new nightly) a lot of start-up noise, can this be avoided, fixed ?


    (browse_tracker_toolbar): Image "images/svg/prev.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (browse_tracker_toolbar): Image "images/svg/next.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (browse_tracker_toolbar): Image "images/svg/mark.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (browse_tracker_toolbar): Image "images/svg/mark_prev.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (browse_tracker_toolbar): Image "images/svg/mark_next.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (browse_tracker_toolbar): Image "images/svg/mark_clear.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (fortran_project_toolbar_22x22): Image "images/svg/fprojectjumpback.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (fortran_project_toolbar_22x22): Image "images/svg/fprojectjumphome.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (fortran_project_toolbar_22x22): Image "images/svg/fprojectjumpforward.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (incremental_search_toolbar): Image "images/svg/incsearchclear.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (incremental_search_toolbar): Image "images/svg/incsearchprev.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (incremental_search_toolbar): Image "images/svg/incsearchnext.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (incremental_search_toolbar): Image "images/svg/incsearchhighlight.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (incremental_search_toolbar): Image "images/svg/incsearchselectedonly.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (incremental_search_toolbar): Image "images/svg/incsearchcase.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (incremental_search_toolbar): Image "images/svg/incsearchregex.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (nassi_shneiderman_toolbar): Image "images/svg/selecttool.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (nassi_shneiderman_toolbar): Image "images/svg/instrtool.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (nassi_shneiderman_toolbar): Image "images/svg/iftool.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (nassi_shneiderman_toolbar): Image "images/svg/switchtool.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (nassi_shneiderman_toolbar): Image "images/svg/whiletool.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (nassi_shneiderman_toolbar): Image "images/svg/dowhiletool.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (nassi_shneiderman_toolbar): Image "images/svg/fortool.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (nassi_shneiderman_toolbar): Image "images/svg/blocktool.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (nassi_shneiderman_toolbar): Image "images/svg/breaktool.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (nassi_shneiderman_toolbar): Image "images/svg/continuetool.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (nassi_shneiderman_toolbar): Image "images/svg/returntool.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (nassi_shneiderman_toolbar): Image "images/svg/glassptool.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (nassi_shneiderman_toolbar): Image "images/svg/glassntool.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (nassi_shneiderman_toolbar): Image "images/svg/sourceToggletool.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!
    (nassi_shneiderman_toolbar): Image "images/svg/commentToggletool.svg" with size [16x16] doesn't match requested size [24x24] resizing (scale factor 1.000)!