Recent Posts

Pages: 1 2 3 [4] 5 6 7 8 9 10
31
Nightly builds / Re: The 27 May 2026 build (13855) is out.
« Last post by eckard_klotz on July 20, 2026, 12:52:33 pm »
Hello Miguel Gimenez.

Quote
... Relating margin order, I prefer it as is. ...

  • It is not the order but the unwanted firing of folding, that is disturbing.
  • An unwanted folding means always to breakdown the development-flow.
    • Suddenly and unexpected the text-part, you want to edit, is vanishing.
    • Instead of of implementing your idea, you have to unfold again.
    • Than you have to search for the text-position you wanted to work on.
    • Finally, by clicking on it, you risk to fold again.
    • I know nobody who is not frustrated by this.
  • Moving the folding margin to the left and away from the text area prevents this nasty disturbance.

If you prefer the current margin order but your users not the alternative will be to make the margin order configurable.
But I fear this will mean much more effort for you.
Thus, I just ask you to solve the folding issue and changing the margin order is a simple way to fix the issue without disabling the folding completely.     

Best regards,
                   Eckard Klotz.
32
Development / Re: Multiple declarations/definitions of wxSwitcherDialog
« Last post by Miguel Gimenez on July 20, 2026, 10:12:15 am »
Spam reported to moderator.
33
Development / Re: Multiple declarations/definitions of wxSwitcherDialog
« Last post by AlexMazure on July 20, 2026, 03:33:45 am »
I've been unwinding lately with a puzzle game called Block Blast. There's something so satisfying about clearing rows and keeping the board from filling up. It's a great way to focus. Speaking of unique implementations, what are your thoughts on handling similar class names in different contexts?

34
General (but related to Code::Blocks) / Re: Delete a ticket on 'CodeBlocks/Tickets'
« Last post by LETARTARE on July 19, 2026, 11:24:19 pm »
Thanks
35
General (but related to Code::Blocks) / Re: Delete a ticket on 'CodeBlocks/Tickets'
« Last post by Miguel Gimenez on July 19, 2026, 09:06:26 pm »
Deleted.
36
Nightly builds / Re: The 27 May 2026 build (13855) is out.
« Last post by Miguel Gimenez on July 19, 2026, 08:55:51 pm »
I have increased margin size from 16 to 22 and made it dependent on scale factor, see r13915.

EDIT: Clicking in the gap between the fold box and the text editor still fires folding  :o , so this change only fixes box size in HiDPI. Relating margin order, I prefer it as is.
37
Nightly builds / Re: The 27 May 2026 build (13855) is out.
« Last post by eckard_klotz on July 18, 2026, 12:35:10 pm »
Hello Developers.

Unfortunately the folding margin is located next to the text inside the editor and thus, it happens very easily that you force a folding even you just want click at the first line position, what is very annoying.

While reviewing the current margin configuration in cbEditor.cpp, I noticed that Code::Blocks defines its own margin IDs:

Code
#define C_LINE_MARGIN      0
#define C_MARKER_MARGIN    1
#define C_CHANGEBAR_MARGIN 2
#define C_FOLDING_MARGIN   3


As far as I understand it, Scintilla (and wxScintilla) always render margins strictly in ascending ID order.
Because of this, the folding margin (ID 3) appears directly next to the text area in the editor. This placement makes it easy to accidentally trigger fold/unfold actions when clicking near column 1, especially on high‑resolution displays.

Other Scintilla‑based editors (SciTE, Geany, Notepad++) avoid this issue by placing the folding margin immediately to the right of the line‑number margin. This provides a natural buffer zone and significantly reduces accidental folding.

In Code::Blocks, the folding margin is configured here:

Code
control->SetMarginType(C_FOLDING_MARGIN, wxSCI_MARGIN_SYMBOL);
control->SetMarginWidth(C_FOLDING_MARGIN, foldingMarginBaseWidth);
control->SetMarginMask(C_FOLDING_MARGIN, ...);
control->SetMarginSensitive(C_FOLDING_MARGIN, 1);


Since all margin‑related logic consistently seems to use the symbolic constants (C_FOLDING_MARGIN, C_MARKER_MARGIN, etc.), adjusting the margin order is limited to changing the four #define values. No other code changes should be required, and no plugins or configuration files are affected.

Suggested improvement: 
Reassign the folding margin to a lower ID (e.g., 1), so the margin order becomes:

Line numbers → Folding → Marker → Changebar → Text


This can simply be changed while the definition of the preprocessor constants like this:

Code
#define C_LINE_MARGIN      0
#define C_FOLDING_MARGIN   1
#define C_MARKER_MARGIN    2
#define C_CHANGEBAR_MARGIN 3


I think this small, isolated change would align Code::Blocks with common Scintilla practice and improve usability without introducing new settings or breaking existing functionality.


Please take a look to this and thank you in advance.

Best regards,
                   Eckard Klotz.
38
General (but related to Code::Blocks) / Re: Delete a ticket on 'CodeBlocks/Tickets'
« Last post by LETARTARE on July 18, 2026, 11:11:22 am »
Thanks :
992
1262
1265
1362
1433
1440
39
General (but related to Code::Blocks) / Re: Delete a ticket on 'CodeBlocks/Tickets'
« Last post by Miguel Gimenez on July 18, 2026, 10:55:22 am »
Post the ticket numbers.
40
General (but related to Code::Blocks) / Re: Delete a ticket on 'CodeBlocks/Tickets'
« Last post by LETARTARE on July 18, 2026, 08:46:40 am »
No,I wanted to make room for my unresolved tickets that had become useless.
Pages: 1 2 3 [4] 5 6 7 8 9 10