Bug #11205 2007-05-28 20:51
bughunter2
Code Completion toolbar - not loading functions
When opening a project, the files you had opened before closing Code::Blocks will be reopened. When Code::Blocks is fired up and a file is open, normally you can select a function you want to go to from the Code Completion toolbar, but it's empty in this case.
IMPORTANT:
This only happens when a project is opened from the Windows Explorer (in my case), NOT when Code::Blocks is already opened.
- Category
- Application::Interface
- Group
- Status
- Closed
- Close date
- 2007-06-20 09:12
- Assigned to
- biplab
History
Can't reproduce this bug in latest revision. Please mention the revision number, OS, wx version.
If possible upload a sample project to reproduce this bug.
CB rev: 4007
wx version: 2.8.3
OS: WinXP SP2
I am just opening a CB project file from the Windows Explorer, the file that is active in the editor has some functions in it, but they are not listed in the Code Completion toolbar.
Though, by simply right-clicking the Tab of the file in the editor and dismissing the context-menu that pops up and then returning focus to the editor will activate the procedure that loads the functions into the Code Completion toolbar.
Where should I upload a sample project? By the way I think its not a problem with project files because it occurs with every project file.
I can confirm this too.
CB rev: 4008
wx version: 2.8.4
OS: WinXP SP2
Thanks to both of you for your feedback. I'll try to reproduce it again.
From *bughunter2*'s feedback, it seems C::B is not receiving focus when it's loaded via DDE.
Well, when I set focus to the C::B editor, it won't load anything either in the Code Completion toolbar :(
Ok, I could finally reproduce this problem. The bug is very complicated one. So don't expect a quick solution though.
The problem is that during opening project through Windows Explorer, EditorOpen event is not thrown. I also suspect that the projectopen event is also not thrown.
Update: The events are generated successfully. The bug is due to some other problems.
A fix is under testing. :-)
This bug is now fixed in HEAD.
Thank you for reporting it.