Activity for Code::Blocks
-
Yurii Koss posted a comment on ticket #1590
I just tried to download that build but something went wrong. Firstly, when I tried to unzip any files in folder "Program Files" it just says "Access denied". Secondly, when I unziped files in another folder that build immediatly suggested me to install a few more plugins and compiler just didn't work. What should I do?
-
Code::Blocks released /Binaries/Nightlies/2026/CB_20260306_rev13810_win64.7z
-
Miguel Gimenez modified ticket #1590
Codeforces 25.03 layout bug with wxWidgets
-
This was fixed in [r13739] last september, you can use a recent nightly.
-
Codeforces 25.03 layout bug with wxWidgets
-
pecan modified ticket #1589
Multiple keyboard shortcuts not saved properly
-
ollydbg committed [r13810] on SVN Repo
- wxSmith: fix build error against wxWidgets 3.3.2 library
-
- clangd_client: cleanup using -Wextra, no functional changes
-
- codesnippets: correct copy .zip error in post build steps
-
- Set svn:executable property in update33 batch files.
-
- CodeSnippets: Restore svn:executable properties on Linux batch files.
-
removing the FortranProject folder creation from checkout
-
* cbp: add the unified CodeBlocks cbps for Windows OS. (thanks gd_on)
-
- remove the usage of $(CODEBLOCKS) in the *.cbp files, because the $(CODEBLOCKS) points to the host Code::Blocks path, not the built Code::Blocks path
-
Gmeeorh created ticket #1589
Multiple keyboard shortcuts not saved properly
-
- Squirrel: Fix compilation with wxWidgets 3.3.2 (thanks Xaviou/Claude).
-
- codesnippets: remove use of $(CODEBLOCKS) CB variable in .cbp for ollydbg
-
-
- codesnippets: place comment in update32_64.bat
-
- codesnippets: commit missing update files
-
- codesnippets: Add right-click context popups and clean up code
-
Crash in wxRecursionGuard in clangd_client
-
Fixed svn 13797, thanks ollydbg
-
* clangd_client: Fix crash in wxRecursionGuard caused by wrong cross-thread protocol
-
Experimental patch
-
-
Crash in wxRecursionGuard in clangd_client
-
Fix patch 1: Index: src/LSPclient/client.cpp --- src/LSPclient/client.cpp (revision 13794) +++ src/LSPclient/client.cpp (working copy) @@ -1,3 +1,4 @@ +#include <memory> #include <ctime> #include <iomanip> #include <sstream> @@ -938,8 +939,8 @@ void ProcessLanguageClient::OnClangd_stderr(wxThreadEvent& event) // ---------------------------------------------------------------------------- {</sstream></iomanip></ctime></memory> std::string* pErrStr = event.GetPayload<std::string*>();</std::string*>...
-
Crash in wxRecursionGuard in clangd_client
-
- Compiler: Fix text shown in dialog.
-
* wxSmith: Allow twildcard translation in wxFilePickerCtrl.
-
Font size in debugger windows is excessively large and cannot be changed
-
Fixed in [r13794]. Fixed also popup's size in HiDPI.
-
* Debugger: Really use configured font in watches' tooltips (ticket #1586, thanks pecan/Gemini).
-
Yesterday and today I've run the the following patch with three different debuggers (debugger_gdb, debugger_gdbmi, and debugger_DAP) and they all appear happy: m_grid = new wxPropertyGrid(this, idTooltipGrid, wxDefaultPosition, FromDIP(wxSize(200, 200)), wxPG_SPLITTER_AUTO_CENTER); wxString fontStr = cbDebuggerCommonConfig::GetValueTooltipFont(); //Geimini 2026/02/16 4 lines wxFont font; if (font.SetNativeFontInfo(fontStr)) m_grid->SetFont(font); So, Miguel, if you agree, please format and apply...
-
IMHO using FromDIP(wxSize(200, 200)) in line 1336 is better for HiDPI.
-
-
Font size in debugger windows is excessively large and cannot be changed
-
I saw cbDebuggerCommonConfig::GetValueTooltipFont() was never called outside configuration, but did not find where the tooltips were created. I see now they are property grids in popups, strange... Good job.
-
Codeblock crashing when returning to main.cpp
-
Compiler plugin : renaming a compiler deletes all its personal configuration datas .
-
Committed r13793. Sorry for the delay. Thanks for your contribution. Happy Chinese New Year!
-
* apply patch #1508: Compiler plugin : renaming a compiler deletes all its personal configuration data . (Thanks homertp)
-
Gemini 3 is suggesting this change. I'll apply and test for awhile. Any comments about this would be appreciated. ✦ The function cbDebuggerCommonConfig::GetValueTooltipFont() works by retrieving the system's default GUI font, reducing its size by 3 points (with a minimum of 7 points), and returning this smaller font description string unless a custom font is saved in the configuration. The reason the tooltip font appears too big is that this function is not actually used in the ValueTooltip class...
-
Gemini 3 is suggesting this change. I'll apply and test for awhile. Any comments about this would be appreciated. ✦ The function cbDebuggerCommonConfig::GetValueTooltipFont() works by retrieving the system's default GUI font, reducing its size by 3 points (with a minimum of 7 points), and returning this smaller font description string unless a custom font is saved in the configuration. The reason the tooltip font appears too big is that this function is not actually used in the ValueTooltip class...
-
I'll see if Gemini 3 will tell me why the ValueToolTip font is too big.
-
- SDK: Fix misleading indentation.
-
* SDK: Check string length before accessing characters by index.
-
* SDK: Do not delete an unallocated object (g_null_log is an static member).
-
- SDK: Fix some warnings, pass wxString by const reference.
-
scriptedwizard : ensure header guard macro is a valid C identifier
-
Applied in [r13788], thank you.
-
* Scripted wizard: ensure header guard macro is a valid C identifier (ticket #1587, thanks Christo).
-
Christo created ticket #1587
scriptedwizard : ensure header guard macro is a valid C identifier
-
RoyalX posted a comment on ticket #1586
Yes, I agree with you that it’s quite easy to create a pull request on GitHub — you just fork the repository, make your changes (patches), and then submit a pull request.
-
C::B is still using svn, and I suggest C::B to use git. And we can have pull request like in github. While, building C::B under C::B is simple, I'm not sure how you build C::B.
-
patches welcome On SourceForge everything feels so confusing and deliberately overcomplicated, unlike GitHub, that it completely discourages contributing to the source code. It seems that just understanding the structure of the C::B project and building it from source would require an enormous amount of time.
-
Font size in debugger windows is excessively large and cannot be changed
-
Dialogs fixed in [r13787]. The tooltip part is pending (patches welcome).
-
* Debugger: Fix font sizes in HiDPI (ticket #1586).
-
Font size in debugger windows is excessively large and cannot be changed
-
* sdk: handle empty valued members in global compiler variable
-
Evaluate expression under cursor
-
Evaluate expression under cursor
-
Evaluate expression under cursor
-
Font size in debugger windows is excessively large and cannot be changed
-
-
* wxSmith: Fix overriding of GetValueString() with wxWidgets 3.3.1 and newer.
-
* clangd_client ClassBrowser Fix asserts caused by invalid wxTreeItemId(s)
-
* clangd_client Fix wrong function call in last commit
-
Thanks, My bad. Corrected in rev 13782
-
* clangd_client Move some of ticket 1585 to the correct position (thanks Christo)
-
Hi Pecan, in rev 13781, shouldn't then change made under textDocument/signatureHelp be done in under textDocument/hover instead?
-
clangd_client : intermittently hover popup persists after switching editor
-
Applied rev 13781. I now remember that I was peeved that the LSP hover response did not include the URI of the request like other responses. Thanks for the fix
-
* clangd_client: Apply ticket 1585 fixing stuck hover popup (thanks Christo)
-
clangd_client : intermittently hover popup persists after switching editor
-
clangd_client : intermittently hover popup persists after switching editor
-
clangd_client : intermittently hover popup persists after switching editor
-
- wxsmith: Refactor wxscolourproperty.cpp and fix some methods that did not override.
-
-
Issue happens when hover request is sent and immediately after that, editor is switched. When the response comes, active editor is different from the requested editor, but the hover popup is shown. The patch ignores any hover response after editor switch by making sure that owner editor of the request is still the active editor when response arrives.
-
clangd_client : intermittently hover popup persists after switching editor
-
- Compiler: Fix two typos in translatable string.
-
Win-7 : Linker, Command line too long
-
Applied in [r13778], thank you.
-
* Fix response file creation when local variables are used (ticket #1584, thanks LETARTARE).
-
Morten MacFly modified ticket #1567
DARK MODE PLS
-
Implemented in SVN, [r13777] . Closing therefore. Note: Only available for wx3.3.x a above.
-
* implemented dark/light-mode for C::B as provided by wxWidgets version v3.3.x and above (closes FR#1567)
-
LETARTARE created ticket #1584
Win-7 : Linker, Command line too long
-
CodeBlocks does not start on Linux (wxSmith plugin broken)
-
After [r13775] works on Tumbleweed, see this post.
-
- wxSmith: Use black icon if loading fails.
-
Commit [r13775] is the first step on finding a solution.
-
* wxSmith: Delay-load images so they are loaded after C::B is initialized.
-
If you need a portable version of Code::Blocks, you can download C::B nosetup.zip.
-
- Reduce threshold of response file triggering (thanks viwrap).
-
That is correct and it used to be my part of updating this control. However, the underlying scintilla did a huge change starting with a certain version (I don't recall at the moment) that I was unable to port to C::B. Maybe its worth another trial or, another option, accept that we loose some features of the (custom) control we use and switch to the "native" scintilla control that wxWidgets ships meanwhile (which wasn't the case for a long time another reason why there was/is a specific C:B control)....
-
That is correct and it used to be my part of updating this control. However, the underlying scintilla did a huge change starting with certain version that I was unable to port to C::B. Maybe its worth another trial or, another option, accept that we loose some features of the (custom) control we use and switch to the "native" scintilla control that wxWidgets ships meanwhile (which wasn't the case for a long time another reason why there was/is a specific C:B control). These are the options we ha...
1 >
