Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign
CC plugin interface redesign
Alpha:
Tooltips are mostly migrated to the new CCManager; it functions almost exactly the same, except for a few of my improvements that should make CC tooltips try to be the optimal size/shape when squished into small monitors. (To compile, you may have to patch the appropriate build system; I only added the files to the unix cbp currently.)
oBFusCATed:
1. Please don't use wxArrayXXX it is bloody dangerous, because there is only one operator[], which is const and which returns a reference to the element. This allows the user to change the content of a const wxArrayXXX. This has led to very mysterious bugs in the past. At least this is the situation in wx2.8. They might have fixed it in 2.9, but I doubt. Use std::vector<wxString> instead.
2. Do you still display the current parameter bold?
Alpha:
1. Sorry, I forgot you had asked that; I will switch it.
2. Only the tooltips (show full name of symbol under mouse) have been migrated. The calltips (which show bold parameters) are currently still provided by the CC plugin.
oBFusCATed:
Hm, I'm a bit confused here...
What is the difference between a calltip and a tooltip?
I don't think there is any and the code should be combined somehow :)
Alpha:
--- Quote from: oBFusCATed on July 15, 2013, 02:54:10 pm ---What is the difference between a calltip and a tooltip?
--- End quote ---
Not much, really. They used to be more different: calltips would only show when you either type '(' after a function, or press Ctrl-Shift-Space; and tooltips by a mouse dwell event. However some time ago, I changed the mouse dwell to also show calltips if no tooltips are available. The main difference at the source level is that calltips have an extra section of code specifying what needs to be highlighted.
I will look to see how easily these could be merged.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version