Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

code completion lately not that good

(1/5) > >>

killerbot:
I have been suffering from this the last couple of weeks. After working a while with CB, activating, switching between different projects the codecompletion gives up on me.
Always "still parsing", even open include file no longer works. Basically one might say : it is dead.

I have codecompletion on all projects on workspace activated, since otherwise it is usable for less then 50%.

Anyone else noticed this, or for our code completion gurus, any fixes already in the pipeline ?

EDIT : to give you an idea on how bad it is : find implementation/declaration of a method which is declared/defined/implemented 50 lines above fails :-(

ollydbg:
Morten has send loaden and me with some similar bug.
I will check it, but seems it is not easy to catch such bug. :D

Loaden:
Works well here.
I need some test code, or more information.

Jenna:

--- Quote from: killerbot on June 23, 2011, 02:29:58 pm ---EDIT : to give you an idea on how bad it is : find implementation/declaration of a method which is declared/defined/implemented 50 lines above fails :-(

--- End quote ---

I did not mention the issue described first (but I do not use C::B very much at the moment), but the can-not-find-declaration-or-implementation-issue happens really often.

MortenMacFly:

--- Quote from: Loaden on June 23, 2011, 04:10:32 pm ---Works well here.

--- End quote ---
@killerbot: I realised the same and there was an issue with the command to obtain the compiler macros which Loaden and I fixed in r7246. So in case you didn't try that revision, please try again.

Furthermore, try to disable both macro options in CC and look, if it's the same.

Unfortunately I have another freeze to add:
When you open a project quickly and then directly open a file from the project before the compiler dirs are parsed C::B freezes very often in my case and you have to kill it via the task manager. This happened to me even today with a hello world console project! :shock:It seems to happen even more often if you have a huge workspace, e.g. C::B and all contrib plugins. It is not reproducible, all I can say that high HDD work load seems to make this happen more often. And no luck with debugging: The debugging version seems always to work.

Navigation

[0] Message Index

[#] Next page