Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign
some issues and requests
oBFusCATed:
Another feature request (question).
--- Code: ---std::vector<someclass>::iterator it = myvector.begin();
it->|
--- End code ---
Does current code completion parse the overloaded -> operator?
Also does it show the methods/members of someclass, not the iterator's?
This will be event better improvement, because iterators are used more often than smart pointers :)
blueshake:
I will dig into it this weekend。
killerbot:
--- Quote from: oBFusCATed on September 08, 2010, 12:19:07 am ---Another feature request (question).
--- Code: ---std::vector<someclass>::iterator it = myvector.begin();
it->|
--- End code ---
Does current code completion parse the overloaded -> operator?
Also does it show the methods/members of someclass, not the iterator's?
This will be event better improvement, because iterators are used more often than smart pointers :)
--- End quote ---
this is an excellent idea.
I have to say I have seen very nice improvements on the cc branch. It is really way better then before :-)
Congratulations to the cc gurus !!!
I do think I found something which is not 100% procent correct. It has to do with the CC toolbar/dropdown.
For example I have a file [c file in this case], so the scope say "global" : OK.
When I position the cursor in the different functions, the toolbar updates correctly, and when I select a method from the toolbar the cursor jumps to the function, all OK.
BUT when I position the cursor between 2 functions, the toolbar doesn't show a function [acceptable since we are in between functions], BUT the drop down list is empty. Since I was still at the global scope, the dropdown list should still contain all the functions. Right ?
MortenMacFly:
--- Quote from: killerbot on September 08, 2010, 10:41:52 am ---I have to say I have seen very nice improvements on the cc branch. It is really way better then before :-)
Congratulations to the cc gurus !!!
--- End quote ---
True, however, I am still facing random crashes. Unfortunately not always. They are of two kinds:
1.) a compiler error occurs and the file in question is opened by C::B automatically. Result: C::B either crashes or freezes. This happens to me often for winbase.h and/or cstdint (the latter only when NOT using the C0XX compiler switch).
2.) a compiler warning/note occurs in the logs and I click on e.g. a note which opens the file in question, too. Result is the same as above but it'll always crash, not freeze.
In both cases the trace log is useless unfortunately. In both cases it works when having CC disabled.
I told Loaden about this but unfortunately he cannot reproduce. He sent me a patch I should try for a solution (actually related to refactoring), but it didn't work.
So: Is it only me or can anybody else reproduce this, too? I am using SVN HEAD of the CC branch, no additional things.
ollydbg:
--- Quote from: MortenMacFly on September 08, 2010, 01:57:33 pm ---
--- Quote from: killerbot on September 08, 2010, 10:41:52 am ---I have to say I have seen very nice improvements on the cc branch. It is really way better then before :-)
Congratulations to the cc gurus !!!
--- End quote ---
True, however, I am still facing random crashes. Unfortunately not always. They are of two kinds:
1.) a compiler error occurs and the file in question is opened by C::B automatically. Result: C::B either crashes or freezes. This happens to me often for winbase.h and/or cstdint (the latter only when NOT using the C0XX compiler switch).
2.) a compiler warning/note occurs in the logs and I click on e.g. a note which opens the file in question, too. Result is the same as above but it'll always crash, not freeze.
In both cases the trace log is useless unfortunately. In both cases it works when having CC disabled.
I told Loaden about this but unfortunately he cannot reproduce.
--- End quote ---
I have heard this bug, but I have never meet this kind of crash. I will try to test more project.
--- Quote ---He sent me a patch I should try for a solution (actually related to refactoring), but it didn't work.
--- End quote ---
Currently, Loaden are testing his new patch, which is V25....(include the refactoring) :D
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version