deb http://apt.jenslody.de/ any dbg
deb-src http://apt.jenslody.de/ any dbg
directorymonitor.cpp: In constructor ‘DirMonitorThread::DirMonitorThread(wxEvtHandler*, wxArrayString, bool, bool, int, int)’:What is going wrong ?
directorymonitor.cpp:102: warning: ignoring return value of ‘int pipe(int*)’, declared with attribute warn_unused_result
directorymonitor.cpp: In constructor ‘DirMonitorThread::DirMonitorThread(wxEvtHandler*, wxArrayString, bool, bool, int, int)’:
directorymonitor.cpp:102: warning: ignoring return value of ‘int pipe(int*)’, declared with attribute warn_unused_result
directorymonitor.cpp: In constructor ‘DirMonitorThread::DirMonitorThread(wxEvtHandler*, wxArrayString, bool, bool, int, int)’:
directorymonitor.cpp:102: warning: ignoring return value of ‘int pipe(int*)’, declared with attribute warn_unused_result
directorymonitor.cpp: In member function ‘virtual void* DirMonitorThread::Entry()’:
directorymonitor.cpp:217: warning: ignoring return value of ‘ssize_t read(int, void*, size_t)’, declared with attribute warn_unused_result
directorymonitor.cpp: In destructor ‘virtual DirMonitorThread::~DirMonitorThread()’:
directorymonitor.cpp:242: warning: ignoring return value of ‘ssize_t write(int, const void*, size_t)’, declared with attribute warn_unused_result
directorymonitor.cpp: In destructor ‘DirMonitorThread::~DirMonitorThread()’:
directorymonitor.cpp:242: warning: ignoring return value of ‘ssize_t write(int, const void*, size_t)’, declared with attribute warn_unused_result
directorymonitor.cpp: In destructor ‘virtual DirMonitorThread::~DirMonitorThread()’:
directorymonitor.cpp:242: warning: ignoring return value of ‘ssize_t write(int, const void*, size_t)’, declared with attribute warn_unused_result
directorymonitor.cpp: In destructor ‘virtual DirMonitorThread::~DirMonitorThread()’:
directorymonitor.cpp:242: warning: ignoring return value of ‘ssize_t write(int, const void*, size_t)’, declared with attribute warn_unused_result
directorymonitor.cpp: In member function ‘void DirMonitorThread::UpdatePaths(const wxArrayString&)’:
directorymonitor.cpp:262: warning: ignoring return value of ‘ssize_t write(int, const void*, size_t)’, declared with attribute warn_unused_result
mv -f .deps/directorymonitor.Tpo .deps/directorymonitor.Plo
Hallo, thanks for new version it's much much more stable than few versions before, but I have noticed a new annoying behavior - when I open or switch to another source file, there is a delay - time in which C::B doesn't respond to anything.when switch a source file/header, CC will do several things:
It looks it is caused by a symbol (function) parser - when I change the filter in symbols window to "Current project's symbols" or to "Everything" the delay is not there.
But when I use "Current file's symbols" the delay is back. I'm sure this wasn't an issue in older versions.
O.K. Now I have noticed the problem is also present if "Current project's symbols" or to "Everything" is chosen - it's enough just to make some change to the file and save it. Now the parser is started and C::B is frozen for a while.
Would it be possible to eliminate the delay - just put the parser to background thread?
I'm using the WinXP version.
Thanks.
when switch a source file/header, CC will do several things:
1, update the toolbar(scope and function)
2, update the symbols browser tree.
But these things should be done in Main thread, because they are UI related.
Can you "disable" the CC's Toolbar to see the delay again?
What exactly you mean by "disable" CC's toolbar?In the "View" menu, uncheck the Code Completion Toolbar to disable it.
QuoteWhat exactly you mean by "disable" CC's toolbar?In the "View" menu, unckeck the Code Completion Tollbar to disable it.
you need to upload the sample project and let us to reproduce this bug, then we can fix it.QuoteWhat exactly you mean by "disable" CC's toolbar?In the "View" menu, unckeck the Code Completion Tollbar to disable it.
Didn't help.
The delay still present.
I have tried also 7017, no change, the delay is still there.
you need to upload the sample project and let us to reproduce this bug, then we can fix it.