Bug #12012 2007-09-17 12:39

yesno

Not-parsing after Application Start / File opening

(For WinXP SP2 and Win2k SP4)

The Symbols Browser (and Code-Completion) doesn't behave as it should do (after NB rev4446).

If you have C::B just opened and no File edited and saved, then

* nothing will appear in the Symbols Tree and

* if you right-click on an #include File (in a subdirectory somewhere)

selecting to open it, you will get an Error Message that the File could not be found, since C::B looks in subdirectory/subdirectory.

If you edit one or more files, then their Symbols will be in the Tree.

(Only the Symbols of these Files. Also, no matter, if you close and reopen them; C::B remembers)

This Not-Parsing and Not-Finding disappears completely and for every File that belongs to the Workspace, if you select "Re-parse now" from the Symbols Pop-up Menu.

Thanks in Advance and with kind Regards

Category

Plugin::CodeCompletion

Group

 

Status

Closed

Close date

2007-10-05 19:25

Assigned to

biplab