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: Formatting fixes and additional check for the statusbar in MainFrame::OnSize
* UI: Fix the placement of the Highlight button in the status bar (ticket #979)
* 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. :(
The regex at sdk/cbeditor.cpp:393 and plugins/contrib/SmartIndent/SmartIndentXML.cpp:54 will fail compiling, because the asterisks need escaping when not used as quantifiers: wxRegEx reUrl(wxT("***:(" wxRegEx reTag(wxT("***:<[ \t]*?(|/)[ \t]*?([a-zA-Z][a-zA-Z0-9_-]*).*?(|/)[ \t]*?>"));
Before going off on a tangent you need to understand the existing code and what it does as it currently shows a few dialogs in batch mode. If the existing code shows message boxes in batch, it is wrong and broken, already. As for 2) you try to build the github code via the batch mode and come back and let me know if the error message in the pop up is useful. Showing messages for CI/batch builds is wrong because the executable gets stuck waiting for someone to press the button. For this and most of...
Before going off on a tangent you need to understand the existing code and what it does as it currently shows a few dialogs in batch mode. As for 2) you try to build the github code via the batch mode and come back and let me know if the error message in the pop up is useful. For this and most of the other changes I do "Think about an end user trying to use the existing C::B functionality and I think that making the changes will make it easier for the end user to use C::B". I am starting to get the...
Showing UI messages in batch mode is wrong. It must not happen. Some people want to use cb batch in CI build, so showing UI messages, breaks those. If the info is not present in the log it should be added.
How ti using patch files
Use the forum for such questions. This place is mostly for reporting bugs/feature request. To be able to use patches first you must learn how to build from source. After that it is probably easy to use patches (if they apply cleanly).
Code blocks gets closed after executing any program.
How ti using patch files
Show first 10 projects that failed to load when loading a workspace
Lexer type combo box in status bar over file name
Status bar problem
Same issue as tickets [#559] & [#767]. These can be reproduced on Windows with SVN [r12468] or Linux Mint 20.1 XFCE with SVN 12458 if you use the maximise and restore down and when restored down change the width of the window and occasionally you get the issue or other corruptions.
Highlighting the active folding block
Fix build on gcc-11: assertion failed: comparison object must be invocable as const
Fixed in [r12303].
You are right, the flags parameter should not be unused, because (at least on windows) it is needed. I fixed this in svn I have also removed the poll timer interval parameter, because it is not needed, i think a fixed value is ok for this... About enum and flags, well i think it is better to use the same type as wxExecute expects or not?
- SDK: increase sdk minor version, fix flags parameter not used, update name of enum value
Check regex validity using wxCHECK_RET() instead of assert()
Should be fixed now. If you find more regexes which fail to compile/work, please report them.
- SDK: Add some statics and do a bit of formatting
* debugger: Fix a regular expression's compilation with wx3.1.6
* SDK: Modify the MacrosManager to compiler regexes only ones (ticket #1120)
* SDK: Fix a regex in the MacroManager to work with the PCRE2 regex engine used by wx3.1.6 (ticket #1120)
* SDK: Put asserts for all regexes in MacrosManager::Reset (ticket #1120)
* regex-testbed: Prevent endless loop if the GetBuiltinMatches causes the window to redraw
- cleanup: Remove unused includes
* regex-testbed: Make sure to pass a valid parent when creating the dialog
- cleanup: Remove and usages of wxT, _T, F from CodeBlocksApp::OnInit
Initialized structure instances breaks code completion
Duplicate of [#33]
bug with codeblocks
Please post about your problem on the forum. Most probably it is a user error. Closing as invalid for now.
bug with codeblocks
Fix regular expressions and operation of the rndgen plugin
Fix Regular Expression Testbed output
* rngden: Fix a format wx-assert and make sure the rndgen action can be undone with a single undo-command
* regex-testbed: Various fixes (ticket #1123, thanks Miguel Gimenez)
* rndgen: Fix issues uncovered by the switch to PCRE2 (ticket #1124, thanks Miguel Gimenez)
Codeblocks Patch for GDB Cygwin exe support
Fixed in master/trunk
* debugger: Fix support for debugging using Cygwin (ticket #909, thanks Andrew Cottrell)
Bug in watchesdlg.cpp
Bug in watchesdlg.cpp
Fix in trunk/master. Please test, especially on dual monitor setups.
- debugger: Replace inline with static, some long line formatting
* debugger: Add clipping to the current display if the Evaluate expression produces a window which is outside of it
* debugger: Make sure the Evaluate expression popup could shrink if the root property is being shrunk (ticket #1100)
* debugger: Make sure Evaluate expression popups doesn't have horizontal scrolls (ticket #1100)
- debugger: Add some consts in watchesdlg.cpp
* debugger: Fix the sizing of the popup shown when evaluating debugger expressions (ticket #1100)
- debugger: Remove checks for wx 3.0.0 in watchesdlg.cpp
Adding a default parameter to the same place where there is another default parameter, and both parameters being the same type is a disaster waiting to happen. Don't do it. Generally don't do default parameters at all. Flag parameters must be unsigned type and most of the time it is best to use something with known and fixed size. Here I guess you're replicating the error wxWidgets people did, I guess.
Batch build stalls when window is not active
@bluehazzard: 1. Any time you change the API/ABI in the include folder you're supposed to rise PLUGIN_SDK_VERSION_MINOR by one 2. What is going on with this flag parameter? - Morten has changed it in to cb_unused in the following commit [r12495], but you've added it in [r12494] one of these commit is wrong - either remove the parameter, or make it do something useful!
- fix for previous commit: The variable pollingInterval is not unused, but flags is instead, so declare as such
Thank you for testing and your comments on the code. this patch is in revision: r12494
Batch build stalls when window is not active
Thank you for testing and your comments on the code. this patch is in revision: 12494