Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign
Patch: function arguments added to autocomplete tooltip
p2rkw:
I tried doxyblocks, but it seems that it only doubles functionality of doxywizard. My question was about display documentation in codeblocks.
to see doc, i.e. description of function parameters I have to minimize c::b and switch to browser, open documentation, search for function, remember parameters meaning and switch back to c::b. My intention was to display documentation in floating window above autocompletion. Something similar to http://netbeans.org/images_www/v7/1/screenshots/editor.png , for example:
And I agree that doxygen is the best tool to generate documentation, and IMO codeblocks should use its to generate docs.
Codeblocks already have (mostly unused) html viewer, maybe it can be used to display documentation? It is possible to make popup floating window with this viewer inside? It can be nice replacement for scintilla's call tip.
dmoore:
I think you could just use a wxPopupWindow. The info windows are popup windows.
oBFusCATed:
I'd be rather careful with the popup window usage... we have very messy fights between the cc and the debugger popups.
Probably you'll have to see what is used to implement the current popup and probably add something to it.
Like a text control at the top/bottom with the comment.
Alpha:
An alternative idea to a popup would be to have a "CC Documentation" tab in the logs at the bottom. CC could update it whenever it felt necessary: docs on the symbol under the caret, docs on the current function, and, of course, docs on the current selection during auto-completion. This idea should not interfere with other popups, but it also may not be as intuitive.
--- Quote from: p2rkw on November 28, 2012, 02:51:14 am ---About documentation, I tried to detect when user changes selection in autocomplete but currently I can't do that.
--- End quote ---
Have you tried the work around of listening for key presses WXK_UP and WXK_DOWN, then requesting the current selection?
p2rkw:
Alpha: yes I did. I added something like this:
Connect(wxEVT_KEY_DOWN, wxKeyEventHandler(CodeCompletion::OnKeyDown));
to Codecompletion's ctor, but my event handler wasn't called.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version