Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
Nightly builds / Re: The 16 Januari 2022 build (12655) is out.
« Last post by Miguel Gimenez on Today at 10:16:29 am »
Only if they generate an assert when debugging.

Searching for "wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL" finds a lot in Fortran project (omitted) and these:
C:\Codeblocks\src\plugins\contrib\SpellChecker\wxspellchecker\src\SpellCheckerOptionsDialog.cpp|89|pSizer->Add(5, 5, 0, wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL|wxALL, 5); // Spacer|
C:\Codeblocks\src\plugins\contrib\cb_koders\kodersdialog.cpp|38|bszIntro->Add(lblIntro, 0, wxEXPAND|wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL, 5);|
C:\Codeblocks\src\plugins\contrib\cb_koders\kodersdialog.cpp|48|bszMain->Add(bszSearch, 0, wxTOP|wxEXPAND|wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL, 5);|
C:\Codeblocks\src\plugins\contrib\cb_koders\kodersdialog.cpp|86|bszMain->Add(bszFilter, 0, wxTOP|wxEXPAND|wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL, 5);|
C:\Codeblocks\src\plugins\contrib\wxSmithContribItems\wxflatnotebook\wxsFlatNotebook.cpp|109|StaticBoxSizer1->Add(Label, 0, wxBOTTOM|wxEXPAND|wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL, 5);|
C:\Codeblocks\src\plugins\contrib\wxSmithContribItems\wxflatnotebook\wxsFlatNotebook.cpp|110|FlexGridSizer1->Add(StaticBoxSizer1, 1, wxLEFT|wxRIGHT|wxEXPAND|wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL, 5);|
C:\Codeblocks\src\plugins\contrib\wxSmithContribItems\wxflatnotebook\wxsFlatNotebook.cpp|114|StaticBoxSizer2->Add(Selected, 1, wxBOTTOM|wxEXPAND|wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL, 5);|
C:\Codeblocks\src\plugins\contrib\wxSmithContribItems\wxflatnotebook\wxsFlatNotebook.cpp|115|FlexGridSizer1->Add(StaticBoxSizer2, 1, wxLEFT|wxRIGHT|wxEXPAND|wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL, 5);|
C:\Codeblocks\src\plugins\contrib\wxSmith\wxwidgets\defitems\wxstreebook.cpp|97|StaticBoxSizer1->Add(Label, 0, wxBOTTOM|wxEXPAND|wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL, 5);|
C:\Codeblocks\src\plugins\contrib\wxSmith\wxwidgets\defitems\wxstreebook.cpp|98|FlexGridSizer1->Add(StaticBoxSizer1, 1, wxLEFT|wxRIGHT|wxEXPAND|wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL, 5);|
C:\Codeblocks\src\plugins\contrib\wxSmith\wxwidgets\defitems\wxstreebook.cpp|102|StaticBoxSizer2->Add(Selected, 1, wxBOTTOM|wxEXPAND|wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL, 5);|
C:\Codeblocks\src\plugins\contrib\wxSmith\wxwidgets\defitems\wxstreebook.cpp|103|FlexGridSizer1->Add(StaticBoxSizer2, 1, wxLEFT|wxRIGHT|wxEXPAND|wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL, 5);|
C:\Codeblocks\src\plugins\loghacker\loghacker.cpp|120|flex->Add(5, 5, 0, wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL|wxALL, 5);|
C:\Codeblocks\src\tools\Addr2LineUI\Addr2LineUIMain.cpp|80|bszReplace->Add(lblReplace, 0, wxBOTTOM|wxLEFT|wxRIGHT|wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL, 5);|
C:\Codeblocks\src\tools\cb_share_config\mainframe.cpp|89|sbsSteps->Add(lblSteps, 1, wxALL|wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL, 5);|

They need a review.
Development / Re: Bug in AddMultipleFilesToProject
« Last post by BlueHazzard on Today at 10:15:34 am »
fixed in trunk
Nightly builds / Re: The 16 Januari 2022 build (12655) is out.
« Last post by AndrewCot on Today at 10:01:41 am »
The following xrc files also have a wxALIGN_CENTER_VERTICAL flag setting in at least one of the spacer widgets in the file:src\plugins\classwizard\resources\new_class.xrc
Do these also need fixing?

Nightly builds / Re: The 16 Januari 2022 build (12655) is out.
« Last post by Miguel Gimenez on Today at 09:17:41 am »
Fixed in [r12678]. wxSmith by default generates horizontal and vertical center flags, and one of them will always raise an assert.
Nightly builds / Re: The 16 Januari 2022 build (12655) is out.
« Last post by Miguel Gimenez on Today at 09:05:35 am »
There are some of these, I fix them when they appear.

I'll take care of it.
Nightly builds / Re: The 16 Januari 2022 build (rev12655) is out.
« Last post by Pecan on Yesterday at 10:38:52 pm »
Running the nightly source (12655) under the debugger gets an assert from Setting/Environment.
Anyone else getting this?

Development / Re: Bug in AddMultipleFilesToProject
« Last post by Miguel Gimenez on Yesterday at 09:19:37 am »
IMHO you are right, this
should be changed to
    if (target != -1)
Plugins development / Re: Code completion using LSP and clangd
« Last post by ollydbg on Yesterday at 03:14:55 am »
This is a code format fix:

 clangd_client/src/LSPclient/src/client.cpp | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/clangd_client/src/LSPclient/src/client.cpp b/clangd_client/src/LSPclient/src/client.cpp
index fadcb51..459b809 100644
--- a/clangd_client/src/LSPclient/src/client.cpp
+++ b/clangd_client/src/LSPclient/src/client.cpp
@@ -702,9 +702,9 @@ void ProcessLanguageClient::OnLSP_Terminated(wxThreadEvent& event_pipedprocess_t
     wxCommandEvent terminatedEvt(wxEVT_COMMAND_MENU_SELECTED, XRCID("idLSP_Process_Terminated"));
-    Manager::Get()->GetAppFrame()->GetEventHandler()->ProcessEvent(terminatedEvt)
+    Manager::Get()->GetAppFrame()->GetEventHandler()->ProcessEvent(terminatedEvt);
-;    if (processExitCode != 0)
+    if (processExitCode != 0)
         wxString msg = "Unusual termination of LanguageProcessClient(LSP) occured.";
         if (lspClientLogFile.IsOpened() )
Plugins development / Re: Code completion using LSP and clangd
« Last post by ollydbg on Yesterday at 03:07:08 am »
@ ollydbg

This change didn't work for me. (Message #69)

I want the codepoint. I don't get any asserts.

With "wxUniChar uniChar(invChar);" I get:
Error: Removed clangd response invalid utf8 char:position(3665), hex(85), U(2026), <cant post> ResponseID:textDocument/completion
Note that I get the codepoint U(2026) back.

With "wxUniChar uniChar(unsigned int(invChar));" I get:

Error: Removed clangd response invalid utf8 char:position(6899), hex(85), U(85), ,<cant post on sf>. ResponseID:textDocument/completion
Here I get only the hex value.

So I changed the wxString::Format to:
msg += wxString::Format("position(%d), hex(%02hhX), U(%x), \'%s\'", invloc, (unsigned int)invChar, (int)uniChar.GetValue(), invStr );
Note the "(int)uniChar.GetValue()"

I'm using wx3.1.5 on windows and wx3.0 on linux.
Works with no asserts.
Does it work for you

In my computer, it works differently than yours.

I did a simple test:

    unsigned char invChar = 0x83;
    wxUniChar uniChar(invChar);

    wxString msg = wxString::Format("hex(%02hhX), U(%x)", (unsigned int)invChar, uniChar.GetValue());


With the above code, the program just pop up an alert (see screen shot in attachment)

While, with below code, it works OK without the alert.

    unsigned char invChar = 0x83;
    wxUniChar uniChar((unsigned int)invChar);

    wxString msg = wxString::Format("hex(%02hhX), U(%x)", (unsigned int)invChar, uniChar.GetValue());


Please note that "Create a character from the 8-bit character value c using the current locale encoding.", which means in my locale encoding, a 0x83 is not a valid Unicode code point, I mean maybe we need two bytes or three bytes to convert it to a Unicode code point.

I'm not sure why in your test case, a 0x83 will becomes a larger value code point U(2026). Maybe, you have different locale encoding as mine. I'm on Windows 7 64bit Chinese language edition, so my local encoding maybe some Chinese language.

Note: it took me 45 minutes to post this. Don't try and post a msg with an invalid utf8 char.  It's a PITA
I also meet this kind of forum error from time to time. So bad.
Plugins development / Re: Code completion using LSP and clangd
« Last post by ollydbg on Yesterday at 02:08:15 am »
The plugin spec says they need to be the same. I cannot remember which OS or if it was the plugin, but case differences have caused me problems. I missed this one when comparing CodeBlocks_wx31_64.cbp and clangd_client_wx31_64.cbp changes for the plugin as my CodeBlocks_wx31_64.cbp has the following line for the output:

                <Option output="devel31_64/share/CodeBlocks/plugins/clangd_client" prefix_auto="1" extension_auto="1" />

For generated files, I prefer the lower case file name format. Since you have the commit right to the svn repo, can you fix them?


The custom variables in build options can be improved from my point of view:

1,  I see "TARGET_DEVEL_DIR_AC" and "TARGET_DEVEL_DIR_PECAN" and "TARGET_DEVEL_DIR" in custom variables. Can we just keep only one variable? I mean we can use a "global variable" in the Menu->Settings->Global variables. This way, we can set those variables by our own setting.

2, the name TARGET_DEVEL_DIR is not correct here. I think "DEVEL_DIR" mainly refer to a folder named "devel31_64" which store the built exe or dlls. So, a better name could be "CB_SOURCE_ROOT" which refer the the root of the svn/git source code root folder.

Pages: [1] 2 3 4 5 6 ... 10