I don't think you need 3 functions, when you can get with 2.
Yes.
When this is done, will I be able use my python CC plugin (after I port it to the new API) alongside the C/C++ CC plugin sharing the same UI?
That is the plan; to allow multiple CC plugins to easily coexist.
Make sure its also interface-compatible to Erans CC works.
Has anyone yet read into the source of his CC, and could give me some pointers? My priority is still mainly on converting the interface/CC plugin within Code::Blocks, but if time allows, I will look into that as well.
Also, people that have used alternate code completion plugins for Code::Blocks (Python, Fortran), do you have any tips as to what components I should be aware of?
Slightly less related: if I have code such as:
int foo = 1;
int MyClass::MyFunction()
{
int bar = 4;
MyInheritedFunction(bar);
}
If I click on
foo so my cursor is outside of
MyFunction(), hovering the mouse over
MyInheritedFunction() usually fails to bring up a tooltip (due to failed lookup of the symbol). However, it (almost) always works if my cursor is, for example, on
bar.
Ideas why?
(By the way, I have committed step one of calltips to my repo; if nothing else, it at least eliminates the annoying multiple blank lines in a row problem.)