Author Topic: Code Completion format  (Read 4162 times)

Encryptor

  • Guest
Code Completion format
« on: September 07, 2006, 08:14:57 pm »
I noticed that in the nightly builds, each line of the Code completion box that pops up has the following format:
<icon> <name> .
When I checked the 1.0rc2 screenshot I saw that the code completion format is:
<method/property> <namespace>::<name> [(params)] : <type> .

I know it's being redesigned, but my question is what format will the final Code completion have? I personally prefer the second one.. I think everyone does :)
Sorry if this was discussed already.. Searching the forum with keywords starting with "Code completion" is almost useless... too many results.
« Last Edit: September 07, 2006, 08:22:21 pm by Encryptor »

Encryptor

  • Guest
Re: Code Completion format
« Reply #1 on: September 10, 2006, 08:32:51 pm »
82 views. No replies (except this one :D). Is the question ambiguous or is there something wrong with it?

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: Code Completion format
« Reply #2 on: September 10, 2006, 09:35:59 pm »
The control on the screenshot, was a custom control which gave us headaches under non-windows platforms. So, we decided to drop it.
Will it ever come back? Who knows...
Be patient!
This bug will be fixed soon...

Encryptor

  • Guest
Re: Code Completion format
« Reply #3 on: September 11, 2006, 01:14:01 am »
Is it possible to modify the current control used,  to display some additional info about the methods/properties?

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: Code Completion format
« Reply #4 on: September 11, 2006, 06:10:33 pm »
Is it possible to modify the current control used,  to display some additional info about the methods/properties?

Nope, it's part of scintilla which we don't want to modify heavily or else scintilla upgrades would be out of the question.
Be patient!
This bug will be fixed soon...