Add three dots button to path field under "User-defined fields" in Global Compiler Variables GUI
See ticket [#1641].
Clarify the name field under section "User-defined fields:" in Global Compiler Variables GUI
Fixed in [r14019]. I have added labels "Name" and "Value" to user vars columns. The value may be a path or anything else, so adding a path selector would confuse the user.
- Global variables: Clarify usage of user vars columns adding Name and Value labels (ticket #1641).
Well, at first sight, it seems to me that it could work. However, my doubt is that I can't understand why doing this change. In my opinion, there are two possible scenarios: If the new script is not good or if we aren't sure that it's right, then we can leave the code as it is, so the old autorevision tool is kept and that's fine. If the new script works fine, then the old autorevision tool is just redundant when using unix autotools for building C::B. The old autorevision tool will still be useful...
- Plugin manager dialog: Fix HTML line in dark mode, some refactoring.
- codesnippets: revert accidental change in Makefile.am from svn 13996
Thanks! i left some notes in blueish text where i documented instances where limiting the checkbox space to its actual area space did not make any change or were not necessary and specially some other GUI bugs unrelated to the check boxes, i forgot to mention that
- SDK: Fix compilation error with wx3.3.
- Limit one more checkbox active area.
Check boxes can be toggled outside of their region in certain areas
Mostly fixed in [r14014]. FortranProject is external, and some checkboxes may went unnoticed.
- Limit checkboxes' active areas (ticket #1647).
- Squirrel: Remove warning in call to memmove().
Check boxes can be toggled outside of their region in certain areas
If you're sure it's the AStyle version and not some other cause, sure. But, from a brief look at Code::Blocks' code, it looks like the Preview rendering and the source code formatting use two different code branches. As I'm not an expert, I'll leave it there...
Creating a new script and inmediately removing it causes a crash
Thanks to you!
Every checkbox turns gray after opening value tooltip font menu under common Debugger settings
All fixed in [r14012], thank you.
* Debugger settings: Fix visual glitch in dark mode when clicking on "Choose" (ticket #1645).
Every checkbox turns gray after opening value tooltip font menu under common Debugger settings
Thanks!
We can update to Astyle 3.6.18, but it requires C++17 for the stupid string_view, and currently we keep C++11 compatibility. I will propose a global change to C++17 in the forum.
Caret in the Syntax highlighting preview doesn't respect the caret settings.
This is a very minor issue, anyway I fixed it in [r14011].
- Syntax highlighting settings: Make the caret match the configured one (ticket #1644).
- ThreadSearch: Fix compilation with wxWidgets < 3.1.6 after r14009.
- ThreadSearch: Use SVG and wxBitmapBundle in toolbar to fix size in HiDPI.
- Debugger_gdbmi: Fix typo.
- SDK: Make strings not translatable.
- Debugger_gdbmi: Fix typo.
- wxSmith: Allow translation of properties from wxHyperlinkCtrl.
Hi @carlo_bramini could you please suggest if attached modified patch and the script is sufficient? It will keep current behavior for normal builds, but use your script during cross compilation.
PATCH: new auto_revision tool for unix-like shells
* wxSmith: Fix event type used in wxHyperlinkCtrl event handler.
I'm building code::blocks for Cygwin and MinGW. For building C::B for Cygwin, I'm using this command: CPPFLAGS=-D_GNU_SOURCE ../codeblocks-code/configure --enable-silent-rules --with-contrib-plugins=all --prefix=$HOME/codeblocks/inst_cb --with-wx-config=/usr/bin/wx-config-3.3-gtk3 --disable-static-wx Unfortunately, C::B uses some C functions that are "extension" or "non standard" for the traditional C library, so I had to add _GNU_SOURCE to CPPFLAGS. Perhaps, a cleaner alternative is adding AC_GNU_SOURCE...
I'm building code::blocks for Cygwin and MinGW. For building C::B for Cygwin, I'm using this command: CPPFLAGS=-D_GNU_SOURCE ../codeblocks-code/configure --enable-silent-rules --with-contrib-plugins=all --prefix=$HOME/codeblocks/inst_cb --with-wx-config=/usr/bin/wx-config-3.3-gtk3 --disable-static-wx Unfortunately, C::B uses some C functions that are "extension" or "non standard" for the traditional C library, so I had to add _GNU_SOURCE to CPPFLAGS. Perhaps, a cleaner alternative is adding AC_GNU_SOURCE...
I updated he patch to codeblocks-code\src\build_tools\autorevision\Makefile.am. Previously, every time auto_revision.sh was executed, it created a new file. So, all executable files created in the previous build step needed to be re-linked even if the file generated by auto_revision.sh was identical to the previous one. This updated patch makes things a bit smarter: if an old source file already exists a it is identical to the current one, then the previous one is not overwritten,
Caret in the Syntax highlighting preview doesn't respect the caret settings.
BTW, <CONTINUATION int="3" /> seems to be ignored. Normally, I have it set to 2, but I pasted the above before setting it back to normal. As a work-a-round, I installed AStyle 3.6.18 and setup Code::Blocks to use it externally. My astylerc file looks like this: indent=spaces=3 indent-continuation=2 indent-after-parens min-conditional-indent=1 max-code-length=95 fill-empty-lines unpad-paren and it formats correctly: some_function(first_argument, second_argument, third_argument, fourth_argument); as...
Hi @carlo_bramini , could you please share the configure command you use for cross compiling codeblocks?
AStyle Indents Differently in Preview than in the Editor
Hello. Any comments?
Add three dots button to path field under "User-defined fields" in Global Compiler Variables GUI
Clarify the name field under section "User-defined fields:" in Global Compiler Variables GUI
- Codesnippets: Fix codeblocks folder case in Unix projects.
- codesnippet: revert 14000
* CodeSnippets: Fix case on Unix projects (thanks LETARTARE).
- codesnippet plugin: change misspelled codeBlocks (Thanks LETARTARE)
Every check box turns gray after opening the font menu
Fixed in [r13999].
* Editor settings: Fix visual glitch in dark mode when clicking on "Choose font" (ticket #1635).
r13998 : replace '_T(' and 'wxT(' for plugins contrib
I have tested on W11 with the last nightly and the problem happens only if you click on the button with the mouse, using the keyboard works fine. Possibly adding a Skip() to the button's event handler fixes this, but ATM I cannot compile C::B with wx3.3. BTW, the issue happens when showing the dialog, not when closing.
r13995 : replace '_T(' and 'wxT('
- Codesnippets: Fix compilation (missing header).
- debugger_gdbmi: add missing files to .cbp and other corrections
- codesnippets plugin: changes/updates for wx33
- Codecompletion: Remove test for TRACE() errors.
- CodeCompletion: Fix compilation after r13991 when TRACE() is not empty.
- dragscroll plugin: Refactor Linux functions for drag operations and safety
* CodeCompletion: Fix crash on startup for macOS Silicon/Rosetta (thanks xsiseux01).
r13988: Replace '_T("...")' by '"..."' in 'codecompletion' plugin
Applied in [r13991], thank you.
r12988: Replace '_T("...")' or '_wxT("...")' by
Applied in [r13991], thank you.
r12984: Replace '_T("...")' by '"..."' in 'autosave' plugin
Applied in [r13991], thank you.
- Plugins: Remove _T() and wxT() (tickets #1636, #1637 and #1638, thanks LETARTARE).
r13988: Replace '_T("...")' by '"..."' in 'codecompletion' plugin
r12988: Replace '_T("...")' or '_wxT("...")' by
r12984: Replace '_T("...")' by '"..."' in 'autosave' plugin
* cbplugn.h: The previous mods to Loggers requires plugins version change to 2.26.0
- Listloggers: Allow ListLogger font color changes (like TextLogger fonts)
I just tried both alternatives of closing the font window. After testing, the results show that the same anomaly occurs; no difference in the behavior.
I am on W7 and cannot use dark mode; Do you close the window using OK or Cancel?. Is there any difference?.
Every check box turns gray after opening the font menu
Thank you. Which compiler did you use? because in the context of 'Linux' I had no warning.
r13984: Replace '_T("")' by 'wxEmptyString' in 'plugins'
Applied (modified) in [r13988], see the commit for more information.
- Plugins: Replace _T("") with wxEmptyString (ticket #1634, thanks LETARTARE).
r12984: Replace '_T("")' by 'wxEmptyString' in 'include'
Patch applied in [r13987], thank you.
- Include: Replace _T("") with wxEmptyString (ticket #1633, thanks LETARTARE).
r13984 : Use of '_T("...")' with 'CB'
Applied in [r13986], thank you.
- SDK: Replace _T("") with wxEmptyString (ticket #1632, thanks LETARTARE).
r13984: Replace '_T("")' by 'wxEmptyString' in 'plugins'
r12984: Replace '_T("")' by 'wxEmptyString' in 'include'
r13984 : Use of '_T("...")' with 'CB'
- wxSmith: fix compilation error in linux autotools build
- wxSmith: Fix wxCommandLinkButton not saving the Note property.
- Main: Add support for dark mode to the start here page.
- Main: Support dark mode in About.
- Main: Support dark mode in splash screen.
- Main: Add splash images for dark mode.
Thanks! hopefully i can start to contribute too