User forums > Using Code::Blocks

code completion settings do not take effect.

<< < (3/4) > >>

ollydbg:

--- Quote from: plainzw on October 15, 2014, 09:31:32 am ---Hi, Alpha, I add the code at the beginning of CodeCompletion::GetProviderStatusFor(cbEditor* ed), and code completion is diabled correctly.

--- End quote ---
Good to see.




--- Quote ---Some member variables about code completion options,  like m_CCAutoLaunch, m_CCAutoLaunchChars, m_CCLaunchDelay, m_CCFillupChars, are declared but never used. I remember these options worked fine in previous revision. I compare working copy with previous copy, and find that they were removed from CodeCompletion::EditorEventHook in rev 9690 as dead code,  so changing these settings of code completion takes no effect.

--- End quote ---
rev 9690 are the code refactoring about CCManager. Yeah, as Alpha said, those options should be put in some SDK's setting dialog.

plainzw:
Yes, I see that some code from CodeCompletion::EditorEventHook is moved to CCManager::OnEditorHook, except reading setting has not been implemented such as auto lauch chars is hard coded.
Then will these settings be removed from code completion setting and create a new SDK setting dialog?

ollydbg:

--- Quote from: plainzw on October 15, 2014, 04:56:00 pm ---Then will these settings be removed from code completion setting and create a new SDK setting dialog?

--- End quote ---
True. We should have a SDK setting dialog for those "common code completion settings". (As we can have many code completion plugins, like native-cc-plugin, clang-cc-plugin, python-cc-plugin, FORTRAN-cc-plugin.)

MortenMacFly:

--- Quote from: ollydbg on October 16, 2014, 08:31:02 am ---True. We should have a SDK setting dialog for those "common code completion settings".

--- End quote ---
...or just file an "CodeCompletion is saving settings" event (where CC plugins can connect to) from CC manager.

ollydbg:

--- Quote from: MortenMacFly on October 16, 2014, 08:35:46 am ---
--- Quote from: ollydbg on October 16, 2014, 08:31:02 am ---True. We should have a SDK setting dialog for those "common code completion settings".

--- End quote ---
...or just file an "CodeCompletion is saving settings" event (where CC plugins can connect to) from CC manager.

--- End quote ---
What does this event used for? Who and to whom?
CCManager to our C++ code completion plugin?

Maybe, an workaround could be that both CCManager and c++ codecompletion plugin share the settings. (configure file)
And CCManager follow the settings in the configure file. Thus, we don't need a SDK setting dialog.

Navigation

[0] Message Index

[#] Next page

[*] Previous page