There is a regression in this build. When I try to go to a function in a file via 'Goto function...' (Ctrl+Alt+G) I now get a pop-up stating 'No functions parsed in this file...'. Interestingly enough, the symbols table is populated correctly and CC is behaving correctly, so CC has parsed the file, somehow the Goto function just doesn't know it.CC has massively changed these days, see the change log in the first post.
Can you give a simple test code to reproduce? thanks!
Can you give a simple test code to reproduce? thanks!
Create a new Win32 GUI project using the wizard and selected a Dialogue based project. Once you've completed the wizard, open main.cpp and hit Ctrl-Alt-G and you should get the pop-up stating 'No functions parsed in this file...'.
Fixed in rev7391. thanks!Can you give a simple test code to reproduce? thanks!
Create a new Win32 GUI project using the wizard and selected a Dialogue based project. Once you've completed the wizard, open main.cpp and hit Ctrl-Alt-G and you should get the pop-up stating 'No functions parsed in this file...'.
Fixed in rev7391. thanks!Can you give a simple test code to reproduce? thanks!
Create a new Win32 GUI project using the wizard and selected a Dialogue based project. Once you've completed the wizard, open main.cpp and hit Ctrl-Alt-G and you should get the pop-up stating 'No functions parsed in this file...'.
Tested the rev 7392, and confirm the fix, great work loaden!Fixed in rev7391. thanks!Can you give a simple test code to reproduce? thanks!
Create a new Win32 GUI project using the wizard and selected a Dialogue based project. Once you've completed the wizard, open main.cpp and hit Ctrl-Alt-G and you should get the pop-up stating 'No functions parsed in this file...'.
Zenju:Indeed, codecompletion seems to blame! If I disable codecompletion, no more hangs!
Can you try to unload the codecompletion plugin and see if the dead locks are gone?
Does the deadlocks happen, when you use CC features?
Can you provide minimal files, which crash/deadlock C::B?Steps to reproduce:
Try to disable symbols browser?QuoteZenju:Indeed, codecompletion seems to blame! If I disable codecompletion, no more hangs!
Can you try to unload the codecompletion plugin and see if the dead locks are gone?
Does the deadlocks happen, when you use CC features?
Steps to reproduce:I can't reproduce the hang on Linux Mint 11 x64 or Win7 x86.
1. open some project. I can reproduce the hang with my own project files (https://sourceforge.net/projects/freefilesync/develop) as well as with a newly wxWigets project by going through the CB wizard.
2. open some .cpp file and change a few lines. It's sufficient to insert arbitrary spaces and newlines. Having something changed seems important. Don't save the changes.
3. Scroll up and down with "PageUp" and "PageDown" keys.
(Repeat 2 and 3 a few times and it will hang.)
I can't reproduce ...This is the biggest problem with data races and all the other threading bugs....
Hi,
I use .cbp generated from cmake-2.8.5 (win32),
and opened by C::B r7385, then the files does not show out all and just some like
-Workspace
- myPrj
- ..
- ..
- app
+ src
+ CMake Files
By using r7288 is OK.
What does I miss on new release?
Thanks
Hi, All, If you found some hangs with CB, please disable the symbols browser.
Hi, All, If you found some hangs with CB, please disable the symbols browser.
If the hang still there, please let's me know.
Sorry for this troubles. :(
Went to <Settings><Editor...><Code Completion><Symbols Browser page> and checked "Disable Symbols Browser" <Ok>.
What are your settings for codecompletion (parser) and symbols browser ?
spectre: Is C::B usable, when run under the control of ThreadSanitizer?
Confirmed...Fixed in rev7413.
Now you should fix the ctrl+shift+. deadlock and CC will be usable, again :)
Great work Loaden, I noticed that you have add the some debug logger like:Confirmed...Fixed in rev7413.
Now you should fix the ctrl+shift+. deadlock and CC will be usable, again :)
+ TRACK_THREAD_LOCKER(s_TokensTreeCritical);
+ wxCriticalSectionLocker locker(s_TokensTreeCritical);
+ THREAD_LOCKER_SUCCESS(s_TokensTreeCritical);
I like the doubleclick on a projet that makes it the main project of the workspace.There is a bug in this process. The macro $PROJECT_DIR (in the Tools) is not synchro with the active project.
Can you try to run C::B with the CC plugin disabled to see it the problems are still there?
3. enumeration values are not properly parsed (only accessible by calling its enumname first irr::video::ECOLOR_FORMAT::ECF_A8R8G8B8 instead of irr::video::ECF_A8R8G8B8)
5. FEATURE REQUEST: all whitespace characters or tabs after last printable character in line should be removed automaticlyThat's possible, activate its setting in the editor settings
7. FEATURE REQUEST: need new feature: select any lines of code and "delete TAB character at start of lines", shortkey SHIFT+TABThat's possible : tab indents, shift tab de-indents
2. FATAL BUG: if i switch from 1 monitor to 2 (or from 2 to 1) all wxWidgets dialogs are set to size 0!!!, so i have to close CB (and hope it wont crash while closing) and reopenConfirmed on windows (XP), but it works on linux (debian 64-it, gnome-shell), so it might be a wxWidgets on windows bug. I will see, if I can look into it.
6. BUG: erasing of tabs with DELETE key does not work (erases always just one whitesspace), even if "use Tab character is marked in settings", the BACKSPACE on the other hand does workThat happens if you do not use tabs, but spaces for indendation (the default), but have "Backspace unindents" checked (also the default).
11. replace of multiple-line-arguments-expressions i.e. replace ";" with "\n{\n\t\return;\n\}\n" does not workWorks fine here, if you check "Regular expression" in the search dialog.
12. BUG: select of multiple line does not work with replace dialog ( "\n", "\t" is replaced with " " and must be corrected by hand)Works here, if I enable "Multi line search" in searchdialog (regexes, seem not to work [correctly|at all]).
13. BUG: find dialogs dont work anyway for project or workspace files (especially the little finddlgs in toolbar "ThreadSearch", "Incremental Search")What does this mean ?
15. hovering over a symbol, CC show its origin or params after a toooooooo long waittime (2-3 sek)The tooltip should be shown after 1s, but it's not configurable (at the moment).
15.1 but leaving the hovered element, this exact info stays on top of window until 3-5sek passed, or i hover over the next element(word) for (2-3 sec),
-> the help text should be removed immedietly, when leaving the element. (thats called interactive^^)
9. BUG: adding ')' character deletes a existing one on that position.Easy: Disable the brace completion option in the editor settings.
It's a bug in wxWidgets, because it does not recognize if a monitor is (dis)connected and therefore can not fetch the correct displaysize.2. FATAL BUG: if i switch from 1 monitor to 2 (or from 2 to 1) all wxWidgets dialogs are set to size 0!!!, so i have to close CB (and hope it wont crash while closing) and reopenConfirmed on windows (XP), but it works on linux (debian 64-it, gnome-shell), so it might be a wxWidgets on windows bug. I will see, if I can look into it.
As a suggestion, dwelltime could be made to feel more "interactive" by having it dynamically change based on the speed/distance the mouse leaves the element - moving the mouse away faster/further would decrease the time the help text is shown.15. hovering over a symbol, CC show its origin or params after a toooooooo long waittime (2-3 sek)The tooltip should be shown after 1s, but it's not configurable (at the moment).
15.1 but leaving the hovered element, this exact info stays on top of window until 3-5sek passed, or i hover over the next element(word) for (2-3 sec),
-> the help text should be removed immedietly, when leaving the element. (thats called interactive^^)
Dwelltime is hardcoded to 1000 ms at the moment, it can be changed easily, but would lead to more config options and therefore to a more confusing settings dialog.
8. BUG: CC helptext is overlapping the actual CB windowsize (tooooooooo long, no linebreak)I have the same problem; code-completion always starts where the cursor is, so when I get to the right side of the screen, half the box ends up off the monitor; hints always begin the box where the mouse is, and as many times these are very long, parts of them also end up off the edge of the screen. It would be useful for hints to contain a line-break function, as well as both hints and code-completion to detect viable display area, and shift left when necessary.
It is here:15. hovering over a symbol, CC show its origin or params after a toooooooo long waittime (2-3 sek)The tooltip should be shown after 1s, but it's not configurable (at the moment).
15.1 but leaving the hovered element, this exact info stays on top of window until 3-5sek passed, or i hover over the next element(word) for (2-3 sec),
-> the help text should be removed immedietly, when leaving the element. (thats called interactive^^)
Dwelltime is hardcoded to 1000 ms at the moment, it can be changed easily, but would lead to more config options and therefore to a more confusing settings dialog.
// static
void cbEditor::InternalSetEditorStyleBeforeFileOpen(cbStyledTextCtrl* control)
{
if (!control)
return;
ConfigManager* mgr = Manager::Get()->GetConfigManager(_T("editor"));
// setting the default editor font size to 10 point
wxFont font(10, wxMODERN, wxNORMAL, wxNORMAL);
wxString fontstring = mgr->Read(_T("/font"), wxEmptyString);
if (!fontstring.IsEmpty())
{
wxNativeFontInfo nfi;
nfi.FromString(fontstring);
font.SetNativeFontInfo(nfi);
}
control->SetMouseDwellTime(1000);
I'm experiencing a very strange bug that happens every 15-30 minutes. I'm not quite sure what's causing it but it seems to be related to copying stuff into the clipboard or while saving documents. CodeBlocks will just hang and WindowsXP will say it's not responding. And he won't. Anymore.
2. FATAL BUG: if i switch from 1 monitor to 2 (or from 2 to 1) all wxWidgets dialogs are set to size 0!!!, so i have to close CB (and hope it wont crash while closing) and reopen
Any update or solution to this problem as this is very annoying.If you read the answers carefully you'll see that this is a bug in wxWidgets. So there is nothing we can do about it for the moment. However, it seems in wx29 this will be fixed.