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

ClangComplete plugin

<< < (8/11) > >>

Folco:
Nice job and thanks Alpha. :)

Lalaland -> these pictures are not a "major part of the experience" for me. I humbly apologise to have another opinion than yours.

Lalaland:
Folco: It is fine, I will add the idea of providing an option to disable the images to the todo list.

ollydbg: Good idea to step through it with a debugger, I can not believe that I did not think of that first.

Folco:
Thanks for that. And congrats for doing such a plugin, it's obviously a huge work.

Alpha:

--- Quote from: ollydbg on November 19, 2011, 05:01:10 am ---This table is quite good, nice work!!!

--- End quote ---

--- Quote from: Folco on November 19, 2011, 02:54:35 pm ---Nice job and thanks Alpha. :)

--- End quote ---
:)

@Lalaland: I have a feature suggestion/request; assuming Clang reports whenever/wherever there is a parsing error, would it be possible for the ClangComplete plugin to put a red marker by the line(s) with errors, or underline (like spell-check) the specific token the error occurs in?

Lalaland:

--- Quote ---@Lalaland: I have a feature suggestion/request; assuming Clang reports whenever/wherever there is a parsing error, would it be possible for the ClangComplete plugin to put a red marker by the line(s) with errors, or underline (like spell-check) the specific token the error occurs in?
--- End quote ---

Feature requesting is a little premature, I have to get the plugin working first.

God, this issue of the menu not popping up in the middle of the word is getting stranger and stranger. The actual issue seems to be that wxScintilla thinks that the word is not being matched(and this is for code completion at the start as well). At the same time, other random words(such as double or class) seem to work. And what really is strange is that the words which works changes determining on where you do the completion.


Here is a video showing what is happening. I turned off autohide, so you can see how wxScintilla does not think anything is matched. I am also using a keyboard shortcut to start autocompletion.

What you will see in this video is me typing in the starts of some keywords that appear in the list of valid completions, and the list correctly moving and highlighting the entry. If it does not do this, then it thinks the word is not in the list, and the list would usually close.
http://youtu.be/kAjb2RwxGqg
(The text at the bottom is showing the string I am passing to show, with '|' set as the separator)

I also double checked the length of the strings churned out by clang. They are the right length as both cstrings and wxStrings, and seem to be fine when printed out(I even tried removing the first character by increasing the cstring by 1, and that worked as expected).

Following the debugger showed that I am putting the right value for the distance to the start of the word, so that is obviously not the issue.

I am truly stumped.
Does anyone have any clue about what is happening?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version