Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign

Patch: function arguments added to autocomplete tooltip

<< < (2/24) > >>

p2rkw:
Ok, I attach corrected patch. Please test it. After patching autocomplete will insert default argument names, so if you want back to old behaviour set 'autoAddArgsNames' to false (line 1507 in codecompletion.cpp).

MortenMacFly:

--- Quote from: p2rkw on November 26, 2012, 03:54:00 pm ---Ok, I attach corrected patch. Please test it. After patching autocomplete will insert default argument names, so if you want back to old behaviour set 'autoAddArgsNames' to false (line 1507 in codecompletion.cpp).

--- End quote ---
Although the functionality might be interesting, please follow our general coding lines.

So (for example) don't add method names with a lower letter, don't add global static functions which can be private to the class and so on... Otherwise the code starts to become really messy and this is not what we want.

oBFusCATed:

--- Quote from: MortenMacFly on November 26, 2012, 08:15:08 pm ---...don't add global static functions which can be private to the class and so on...

--- End quote ---
I don't agree here, global static function are way more private then a private function in the class. I tend to use them a lot.

p2rkw:
I forgot about capital letters, sorry,
I made those 3 functions as static free functions because they don't touch any Codecompletion's non-static and static fields. Moreover they're visible only in codecompletion.cpp compilation unit.

dmoore:
Nice idea, but how do you deal with really long call sigs? Would be nice if the box was horizontally scrollable but that probably requires changes to scintilla. Also, would be really nice to have a second pane that shows doc strings. (see Netbeans)

Navigation

[0] Message Index

[#] Next page

[*] Previous page