Thanks for the links, it seems the discussion is pretty old. Regarding the other forums i go they use 2.0.18, here is one example and it works fine here: http://www.romhacking.net/forum/
The forum uses SMF 2.0.18, native support for IPv6 was added in 2.1.0. See this thread and specially this post in the thread. The other forums may be using the mod or the new version.
Miguel - i dont believe it's a bug with smf, i go to several forums that use SMF and i dont have this problem with them, perhaps a bug in the forum's server?
wxSmith assert when using wxStdDialogButtonSizer in XRC
fixed in r12535 thank you for reporting Andrew Cottrell and thank you for the patch Miguel!
*wxSmith: fix assert in wxStdDialogButtonSizer (fix ticket #1110, thank you Miguel Gimenez)
Fix assert in wxSmith editor when window contains wxStdDialogButtonSizer
duplicate of #1110
My global variable - j1 - are in conflict with your - math.h
For support questions please ask in the forum this is only for bug reports and patches thank you
Remove obsolete workaround in file manager
in revision: 12534 thank you again!
* File Browser: remove workaround for wxRenameFile (apply patch #1137, thanks Miguel Gimenez )
We have a lot of issues with mac... You can search the forum for nightly builds for mac that should work...
Windows CB crash due to floating watch window issue on exit while still debugging
Fixed rev 12533
* core For Windows, close shown floating windows before shutdown to avoid hangs in Hide() and crashes in Manager::Shutdown()
Fix CCManager compilation with C++17
This is fixed in the trunk now, thanks!
* Fix CCManager compilation with C++17(apply patch #1142, thanks Miguel Gimenez)
Fix CCManager compilation with C++17
That error appears if you have a public IPv6 address, it is a bug in the SMF version used. Quoting from the forum: After a transition period of 23 years for IPv6, the ISPs in my region (Germany) only use DS-Lite for new (private) contracts. I just tried to use the search function with a DS-Lite -> database error Then tried to use the search function with a Dual-Stack -> worked after telling firefox network.dns.disableIPv6 = true Then tried to use the search function with an old Telekom 8!!MBit DSL...
That error appears if you have a public IPv6 address, it is a bug in the SMF version used. Quoiting from the forum: After a transition period of 23 years for IPv6, the ISPs in my region (Germany) only use DS-Lite for new (private) contracts. I just tried to use the search function with a DS-Lite -> database error Then tried to use the search function with a Dual-Stack -> worked after telling firefox network.dns.disableIPv6 = true Then tried to use the search function with an old Telekom 8!!MBit DSL...
That error appears if you have a public IPv6 address, it is a bug in the SMF version used. Quoiting form the forum: After a transition period of 23 years for IPv6, the ISPs in my region (Germany) only use DS-Lite for new (private) contracts. I just tried to use the search function with a DS-Lite -> database error Then tried to use the search function with a Dual-Stack -> worked after telling firefox network.dns.disableIPv6 = true Then tried to use the search function with an old Telekom 8!!MBit DSL...
Hi Andrew - a pity the fixes arent in the source code. Thank you for replying and for the link to the unofficial installer.
Hi Miguel - i did what you suggested before you replied and even so CB wasnt able to find the compiler. Thank you for replying and for the link to the build too, i'm having problems with several sections of the forum who give me the error you can see in the pic.
Depending on which compiler you have installed depends on the exact fix required in C::B. Unfortunately the fix/fixes have been available for a while now, but have not been incorporated into the C::B source code. More details and info on an unofficial installer that incorporates the Windows compiler detection changes is available on the following forum thread: https://forums.codeblocks.org/index.php/topic,24592.0.html
Make Codef() compilable when wxUSE_STL == 1
in revision: 12531 thank you again!
* wxSmith: Fix compilation with wxUSE_STL == 1 (apply ticket #1138, thanks Miguel Gimenez)
Correct language of wxLED contrib item
in revision: 12530 thank you for your support
* wxSmith: Replace German with English, enable translation (fix ticket #1139, thanks Miguel Gimenez)
This is a known problem. Go to Settings -> Compiler -> Toolchain executables, click on the button with three dots and navigate to the compiler installation path (probably it is in a MinGW folder under C::B installation folder). Check if the names in Program Files tab match those found under MinGW/bin and change them if needed. Regarding the nightly, try this link If you have any doubt please ask in the forum
Codeblock 20.03 32 bit doesnt detect a compiler
Fix CCManager compilation with C++17
after run "hello world" doesnt comes out
Duplicate of ticket 1021, look there for a workaround
Duplicate of ticket 1021, look there for a waorkaround
Error
Correct language of wxLED contrib item
Make Codef() compilable when wxUSE_STL == 1
The error posted is no longer thrown (wx3.1.5, GCC 8.1), but there are a bunch of them related to wxString. wxString "normal" version is implicitly convertible to char * and wchar_t *, but std::string is not, so constructions like pImageNames[i] = (const wxChar *) sImageNames[i]; where sImageNames[i] is a wxString and static const wxChar* PaperIDNames[] = { _("Use specific dimensions"), are invalid. In the first case the solution would be this: pImageNames[i] = sImageNames[i].c_str(); but the latter...
math.h is not part of Code::Blocks, please ask in a forum related to your compiler
Remove obsolete workaround in file manager
My global variable - j1 - are in conflict with your - math.h
I have fixed this in my Windows NSIS installer script. Search the script for "IsWinXP" as XP requires an older set of crash handler files that are compatible with XP.
You need to manually install it yourself.
This occurs in both Linux and Windows Code::Blocks SVN 12529 (SVN trunk built locally on both).
Possible patch: - Do not check compiler validity if the target is skipped - Remove unnecessary calls to F(), _T() and wx_str() - Split long lines
Nice to know that a working GDB version exists, Do I have to install this GDB version myself or has the CodeBlocks installer been updated
Just checked http://wiki.codeblocks.org (without the 's') and it works, showing the https version. Clicking on any link of the wiki leads to the 502 error again, because they point to the https version. EDIT: this fails less fequently but also fails
Just checked http://wiki.codeblocks.org (without the 's') and it works, showing the https version. Clicking on any link of the wiki leads to the 502 error again, because they point to the https version.
Things are getting worse, starting many days ago the wiki cannot be accessed (Cloudflare error 502). Cloudflare help for this error leads to this report: fl=365f7 h=wiki.codeblocks.org ip=2.xxx.xxx.xxx ts=1631701353.907 visit_scheme=https uag=Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:92.0) Gecko/20100101 Firefox/92.0 colo=MAD http=http/2 loc=ES tls=TLSv1.3 sni=plaintext warp=off gateway=off
I have tested the patch and it resolves the issue I reported.
Sorry, I didn't notice ticket 1110; please close this ticket.
I didn't notice this ticket until posting ticket 1135, please close it as duplicate. The fix is easy, just don't add the window to a sizer. Probably all the code related to Outsizer can be removed, everything works without it.
Fix assert in wxSmith editor when window contains wxStdDialogButtonSizer
Please see comments in the forum: https://forums.codeblocks.org/index.php/topic,24603.msg167932.html
Language field in the status bar has random possition after a resize
Should be fixed in trunk now.
- build: Automatic project changes
- A bit of formatting
- build: Add dependencies to thne codeblocks project in the workspace for wx31 64 bit
* UI: Fix initial position of the highlight button in the status bar on macOS/windows
* UI: Remove the call for GetFiledRect while creating the status bar
* UI: Fix a statusbar flicker when opening new files
* UI: Also hide/show the highlight button in the statusbar when it is not needed
- wxSmith: A bit of formatting
* UI: Fix the placement of the Highlight button in the status bar (ticket #979)
- UI: Formatting fixes and additional check for the statusbar in MainFrame::OnSize
* UI: First fix for the status bar problem (ticket #979)
- wx30: Replace wxEmptyString with wxString default c-tors
- Spellchecker: Fix unused parameter warning
I am using the nightly builds downloaded from sourceforge: CodeBlocks 12312 (Before) : Name : Code::Blocks Version : svn-r12312 SDK Version : 2.6.0 Scintilla Version : 3.7.5 Author : The Code::Blocks Team E-mail : info@codeblocks.org Website : http://www.codeblocks.org OS : Windows 10 (build 19042), 64-bit edition Scaling factor : 2.500000 Detected scaling factor : 2.500000 Display PPI : 240x240 Display count : 1 Display 0 (\\.\DISPLAY1): XY=[0,0]; Size=[3840,2160]; Primary wxWidgets Library (wxMSW...
It's an application explorer/package manager in KDE. I reported to kde.bugs.org but it's not their service. I don't know where to report then. https://bugs.kde.org/show_bug.cgi?id=441495#c1
Here it is
HiDPI broken after moving to WxWidgets 3.1.5
OS/Distro? If on linux what is the toolkit. Please copy-paste everything from Help -> About -> Information.
Compiler is checked for skipped targets
Can you provide sample project/workspace which could be used to reproduce the problem?
What is Discover? We (cb devs) don't know about it, neither we ship packages for it.
Same problem on Kubuntu 20.04.3 LTS. It popups window additionally:
Broken install in Kubuntu 21.04 via Discover
Compiler is checked for skipped targets
It is not a good idea to popup every time when a cross-platform project is loaded on Linux while it has Windows targets using msvc compiler.
It is not a good idea to popup every time when a cross-platform project is loaded on Linux while it has windows targets using msvc compiler.
HiDPI broken after moving to WxWidgets 3.1.5
Check regex validity using wxCHECK_RET() instead of assert()
This new version removes _() and wxT() also.
Fix hack in CodeCompletion's regex
Well, I have checked the list of regex with PCRE2 from wxWidgets 3.1.6, and I have found that the three asterisks sequnce compiles with same results when using the test bed plugin. Perl just rejected them. C::B regexes do not show compilation errors. There are problems with many regexes (over 40) from FortranProject, because at least \y and \M are not recognized. I will report this to Darmar.
This issue is resolved now. I was using code blocks 20.xx version on Windows Pro 10. I just uninstalled this and installed 17.xx. I am able to practice C code. Thanks for the attention.
Can you give some more information? What does close? Codeblocks? your Application? What are the exact steps to reproduce? 1) Start codeblocks, 2) Load my project 3) klick build 4) ?????? Can you post the project file (only the .cbp file)?
The list is not complete, I have removed the calculated regexes, and some of the others may be undetected, The new PCRE2 is more picky with syntax, specially about what must be escaped, but this is easily detected via compiling. Once the syntax is correct, the differences are corner cases.
Miguel thank you for the work. I'm not sure an automatic approach to test this would be useful. But having a list of regexes is useful for sure. Unfortunately we'll have to put every regex in the regextest bed and play with it to see if it behaves as expected. Or just wait for people to find the problems. The other option is spending the time to write tests for all the functionality which uses regexes. Which is even more work, but more future proof.
I did the grep of the source code looking for wxRegEx or Compile(), then cleaned, completed the results, made them more parseable and passed the result to a perl script that extracted the expressions and tried to compile them. A better way would be doing the same using wx3.1.6, but currently I have little free time. I have attached the results. This is the script: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31#!/usr/bin/perl use strict; use warnings; # use diagnostics;...
It may be useful to do a grep over the whole cb sourcetree for wxRegEx and check all the results. Has anyone done this yet? Or is it too much?
How have you discovered those? Just stumbled on them in regular use of C::B? I suppose the only reliable solution to this crisis is to actually spend the time to gather all regexes in source code and inspect them one by one. :(