Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign

clangd_client string name inside the codecompletion\parser\cclogger.cpp file

<< < (2/3) > >>

Pecan:
"clangd_client" name and "CodeCompletion" name protected by preprocessor guards, activated only when BUILDING_PLUGIN define is present.

@ollydbg, thanks for the patience.

ollydbg:
Hi, I'm currently code-refactoring the legecy codecompletion plugin's tokenizer.

I see one change by you:


--- Code: ----    CodeBlocksThreadEvent evt(wxEVT_COMMAND_MENU_SELECTED, m_DebugLogId);
+    bool debugLogging = m_pCfgMgr->ReadBool("/logPluginDebug_check", false);
+    if (not debugLogging and (id==m_DebugLogId)) return;

--- End code ---

when the parser finished parsing a project, it normally will print something like: xxxxx tokens and xxxx seconds.

But with this change, I can't see this.

I searched for a while, and I can't find the variable named "/logPluginDebug_check", so what is this purpose of this variable.

For me, I would like to see the debug events from the codecompletion plugin.

Thanks.

Pecan:
@ollydbg
Sorry about this (again).
Please put preprocessor guards around code like that.
I was using it to debug the CodeCompletion plugin and did not consider that it would be used stand-alone.

--- Code: ---#if defined(MAKING_PLUGIN)
   <the offending code>
#endif

--- End code ---

Commit the changes when you are satisfied.
Sorry again.

Pecan:

@ollydbg
Sorry about this (again).
Please put preprocessor guards around code like that.
I was using it to debug the CodeCompletion plugin and did not consider that it would be used stand-alone.

I think the best thing to do is just revert the changes to a version that is usable for you.
I'll do that now.

Pecan:
#ollydbug

Look and set the debug checkbox to see if it solves the problem.
If not, I'll revert to a previous CCLogger with my changes.

Navigation

[0] Message Index

[#] Next page

[*] Previous page