Activity for Teodor Petrov
-
Teodor Petrov posted a comment on ticket #979
Should be fixed in trunk now.
-
Language field in the status bar has random possition after a resize
-
- 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
-
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.
-
Check regex validity using wxCHECK_RET() instead of assert()
-
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.
-
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. :(
-
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...
-
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).
-
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].
-
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.
-
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)
-
Fixed in master/trunk
-
Codeblocks Patch for GDB Cygwin exe support
-
* 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!
-
Add path to auto_detect_compilers.xrc dialog
-
https://github.com/obfuscated/codeblocks_sf/pull/31
-
Andrew Cottrell: If you want any of the sort-of-pull-requests you've posted on various tickets recently to be reviewed by me, you'll have to open actual-PRs on my repo on github.
-
- build: Remove redundant DLLIMPORTs in sc_utils.cpp
-
Compiler selection dialog should not include invalid compilers
-
two build errors under linux
-
* scripting: Print more information when someone calls a native function from squirrel incorrectly
-
- build: Fix compilation with wx-master (ticket #1122)
-
- build: Fix build when using STL enabled wxWidgets (ticket#1122)
-
- sdk: Replace wxEmptyString with wxString and .empty
-
You'll get them if you comment the asserts, you need cb to actually start. Unfortunately they are so async that they aren't really helpful. I'm pretty sure I'll modify my local version to throw an assert, just in case.
-
The main question is what are these two regexes trying to match. I really have no idea. So before going forward we need to answer this question. Also I suppose we'll need to put a wxAssert in the internals of wx, so we can test if other regexes fail to compile. I'm pretty sure there be more of them, but there are more dynamic. :(
-
This is not supported. Even if this is fixed you'll be unable to compile wxSmith and fixing wxSmith doesn't look to be trivial (requires major changes).
-
This is not supported. Even if this is fixed you'll be unable to compile wxSmith.
-
I'll fix both of those, but I don't reproduce the wxArrayString::GetCount() error. Can you extract it from the build log and post it here?
-
There is a discussion about these on wx-dev: https://groups.google.com/g/wx-dev/c/7r414eyrPp4/m/FFCARtpZBgAJ
-
Which revision of codeblocks are you using? --disable-compat30 is probably too much at the moment.
-
Unsurprisingly we're hit by this. If you debug this you'll see a message like this missing terminating ] for character clas It seems even wxRegEx regexFortranArray(wxT("^\\([0-9,]+)$")); is causing problems - it fails to compile, not sure if it worked in 3.1.5.
-
@bluehazzard Would you push this?
-
CDB - threads list and locale vars
-
* SDK: Fix compiler warning
-
* logger: Scroll to the end of log control if a new message is added (ticket #1092)
-
In svn. Thanks for the contribution. Is there anything left to do about this ticket?
-
* debugger: Better parsing the threads list from CDB (ticket #1060, thanks maras420)
-
@jmacc What is VSC? If it is Visual studio Code then it uses the gdb-mi interface, as far as I know.
-
@maras420: Can you provide an explanation what this patch does?
-
FortranProject still referenced in truck workspaces and Makefile.am & update.bat
-
Use svn and it will work.
-
Nope, push as is and lets see if somebody complains first.
-
Probably the fix happened too late for the release. You can use a night build or apply the patch and rebuild.
1 >
