Code::Blocks Forums
Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: tiwag on August 31, 2006, 11:18:38 am
-
thanks for
* putting the symbol browser back to a manager tab
* the "codecompletion" toolbar ( should it not be named ClassBrowser-Toolbar ? )
one small bug which i discovered in CB rev 2925
if you have set the Symbol-Browser to "Current file's symbols"
and you close the current file-tab, then the symbol-browser-tree isn't updated
to the contents of the currently viewing file (this is annoying)
-
( should it not be named ClassBrowser-Toolbar ? )
Unfortunately, the name is currently auto-generated using the plugin's name.
one small bug which i discovered in CB rev 2925
if you have set the Symbol-Browser to "Current file's symbols"
and you close the current file-tab, then the symbol-browser-tree isn't updated
to the contents of the currently viewing file (this is annoying)
Two things to mention regarding this:
1) the issue has to do with SDK events not fired for editor change, unless you click on the editor's tab. Even Ctrl-Tab doesn't fire this event. I have it noticed and will fix it (which will fix this issue too).
2) the current filtering for "current-file-scope" is sub-optimal. Works, but causes a slow down when changing editors or refreshing the symbols browser. This will be improved in future revisions.
-
Two things to mention regarding this:
1) the issue has to do with SDK events not fired for editor change, unless you click on the editor's tab. Even Ctrl-Tab doesn't fire this event. I have it noticed and will fix it (which will fix this issue too).
OK i understand
2) the current filtering for "current-file-scope" is sub-optimal. Works, but causes a slow down when changing editors or refreshing the symbols browser. This will be improved in future revisions.
maybe a lot of wasted time comes from the unfrozen treeview control during update ?
-
maybe a lot of wasted time comes from the unfrozen treeview control during update ?
No, no, it's not that. I know what it is and I even have a TODO in the code for it.
And since this is the last TODO left, it's next on the list ;).
-
And since this is the last TODO left, it's next on the list ;).
And there it goes ;).