Recent Posts

1

General (but related to Code::Blocks) / Re: Welcome Newcomers - PLEASE READ!!!

« Last post by yositoki-mabbe on Today at 03:56:57 pm »

here i am i guess

2

Development / wxWidgets 3.2.5 is out

« Last post by Miguel Gimenez on Yesterday at 07:26:58 pm »

wxWidgets 3.2.5 has been released. I am currently compiling it.

Among many oher changes, wxFloatProperty now uses the correct decimal separator with non-english locales and wxVariant supports VT_UI8.

3

General (but related to Code::Blocks) / Re: patch for the autotools build to work with Msys2/MinGW32

« Last post by Grit Clef on Yesterday at 06:30:38 am »

Good! Simple but useful for me.

4

Plugins development / Re: Code completion using LSP and clangd

« Last post by Pecan on May 16, 2024, 08:27:55 pm »

Hi, thanks.
I just tried this latest revision.

There is still one issue, clangd error and breakpoint happens in the same line. Still they have the same size. One is circle, and the other is a square.

I can't reproduce a clangd warning easily. 

see below image shot:

Same with legacy CC . It's always been that way.
I'd have to change legacy CC use of cbEditor to do anything about that.
I'd prefer not changing legacy CC if I can avoid it.

For me, an obvious code  error (red square) should be corrected before debugging occurs. When the error is corrected, the debugger breakpoint circle appears.

Also you can always use the "Debugging windows" icon (top line main menu, left of info icon) to see your breakpoints listed.

I really do not know how to solves this situation without changing the legacy CC interface (cbeditor) for current users.
Legacy CC is used way more than clangd_client.

Suggestions accepted.

5

General (but related to Code::Blocks) / patch for the autotools build to work with Msys2/MinGW32

« Last post by reckless on May 16, 2024, 05:30:12 pm »

The Msys2 devs dont want it since they are deprecating win32 but for those of us who still use 32 bit sometimes this fixes the build.

the problem as noticed by others is that windres on 32 bit mingw gets passed -mthreads via the WX_CXXFLAGS flag.
changed it to WX_CPPFLAGS as both return the same minus the -mthreads flag.

6

Plugins development / Re: Code completion using LSP and clangd

« Last post by ollydbg on May 16, 2024, 02:45:26 pm »

I prefer Pecan's method "I can change it to a small right pointing arrow that fits inside any other marker".

Commit HEAD 13521:
Clangd_client warning margin marker changed to a small right pointing arrow.

Hi, thanks.

I just tried this latest revision.

There is still one issue, clangd error and breakpoint happens in the same line. Still they have the same size. One is circle, and the other is a square.

I can't reproduce a clangd warning easily. 

see below image shot:

7

Plugins development / Re: Code completion using LSP and clangd

« Last post by Pecan on May 15, 2024, 06:10:46 pm »

I prefer Pecan's method "I can change it to a small right pointing arrow that fits inside any other marker".

Commit HEAD 13521:
Clangd_client warning margin marker changed to a small right pointing arrow.

8

General (but related to Code::Blocks) / Re: Project build options - no available tick boxes for Compiler Flags

« Last post by Miguel Gimenez on May 15, 2024, 01:51:01 pm »

Spam reported to moderator.

9

Plugins development / Re: Code completion using LSP and clangd

« Last post by ollydbg on May 15, 2024, 12:03:28 am »

meaningful workflow during editing/debugging should be the guide to visual appearance.

@ollydbg: What is your take on this? For how long do both markers compete for the spot in your projects? Do either markers last that long that it really matters?

I prefer Pecan's method "I can change it to a small right pointing arrow that fits inside any other marker".

I use C::B for my daily work, and some of the clangd_client warnings come from third part library's source code, so those warnings will last for a long time.

Thanks.

10

Plugins development / Re: Code completion using LSP and clangd

« Last post by blauzahn on May 14, 2024, 09:26:51 pm »

meaningful workflow during editing/debugging should be the guide to visual appearance.

@ollydbg: What is your take on this? For how long do both markers compete for the spot in your projects? Do either markers last that long that it really matters?