Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign
Clang CC
yvesdm3000:
OK I'll hande/implement this first in the plugin, but I'll make sure I can easily move it to C::B later on. This enables me to keep using stock code::blocks and the early adopters have less work following progress since they don't have to patch codeblocks.
Looks like XCode replaces the whole line with the fixit when not yet applied and reverts that if you don't apply it. The choice to apply it is not really a button but a context-menu similar to the CodeCompletion-context-menu.
About the confusion with the error/warning annotations, I would not change the existing behaviour, I treat these fixits as something extra, so there can be an error-annotation saying there is a missing ')' and also a fixit that pre-visualizes the ')' at the end. For now I only need something extra for the 'apply'-button/menu/whatever.
Yves
yvesdm3000:
--- Quote from: l_inc on December 04, 2015, 12:59:30 pm ---As for me a couple of shortcuts would suffice
--- End quote ---
I'm aware we lack operations on these warning/errors. I would at least need goto next/previous error/warning with good shortcuts. It's however pretty confusing since there are also the build error/warnings which are not necessarily from the same compiler.
I also think it would be a good idea to have a separate output view that outputs there errors, similar to the build messages. Maybe some people don't like them to be inlined, it would also give a more global overview of the amount of warning/errors.
Yves
oBFusCATed:
--- Quote from: yvesdm3000 on December 05, 2015, 09:46:13 am ---I also think it would be a good idea to have a separate output view that outputs there errors, similar to the build messages.
--- End quote ---
Please don't do this, we have too many logs already, and I'm sure more people won't like the new log pane, then the integrated annotations!
--- Quote from: yvesdm3000 on December 05, 2015, 09:46:13 am ---Maybe some people don't like them to be inlined, it would also give a more global overview of the amount of warning/errors.
--- End quote ---
You'll have to find a way to reuse one of the compiler logs or even both. Probably we should move them to the sdk somehow.
yvesdm3000:
I compiled a version for Windows now. It seems to work fine but makes CodeBlocks very unstable, disappearing widgets etc... Still need to figure out why that happens before I publish a binary.
Yves
yvesdm3000:
I released an alpha-version for Windows here:
https://github.com/yvesdm3000/ClangLib/releases/tag/0.3.1
All constructive feedback is welcome.
Yves
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version