I have the intention to make a final release based on this night build.Do you plan to make an OS-X release (or do you also need OS-X specific problems reports) ?
Please test it and report as many problems, so we can have a solid release.
Do you plan to make an OS-X release (or do you also need OS-X specific problems reports) ?I plan to make an OSX release, but I first need to fix the bundle.sh to add the contrib plugins.
a) The drop down window for selecting project targets is too small/short. Please allow the scroll box to extend much further (at least 8 -10 lines)in trunk is a version that has a little tool button near the drop down list. There you can search for all targets
b) Please add a "view windows/tabs" item to the toolbar that allows reviewing and navigating directly to open files/tabs.the shortcut "alt+g" is great for finding files
c) The right-click pop up menu has the vastly most common and important controls in a sub menu (e.g. cut/copy/paste), thus it is an unnecessary extra step to use those important features .. repeated hundreds of times each and every session (yes, I do use the key board short cuts, but still). Could those appear at the top level in the pop-up, please?I too find this annoying, but a larger context menu is more annoying. I think 90% who use this menu entries more often should use keys for this...
c) The right-click pop up menu has the vastly most common and important controls in a sub menu (e.g. cut/copy/paste), thus it is an unnecessary extra step to use those important features .. repeated hundreds of times each and every session (yes, I do use the key board short cuts, but still). Could those appear at the top level in the pop-up, please?
... these are relatively minor things, and CB is a great product.
1) SVN 11146 (ie. the previous nightly) crashed frequently. Not 100% certain, but it seemed to be when there was at least two projects open, each a reasonable number of files in disparate locations, and possibly a large number of targets, and a sufficient number of "switching between" etc. I'll let you know if 11176 does this, assuming I can figure how to get access to derlios.de/bug reporting.
2) A long standing "bug" with Fortran (f90) files is that the debug/error list cannot be used (e.g. double click on error) to navigate to the offending line directly. One must do so manually. This was a kind of 50/50 hit and miss with GCC/gFortran etc ver's 4.xx, 5.xx (as reported previously some years ago), but since vers 6.xx and 7.xx (and associated GDB's etc) it almost never works. Oddly, on the rare occasion when it works, it seems to be now only with linker errors.The output is parsed using regular expressions. They could be edited in the advanced compiler options dialog or in
c) The right-click pop up menu has the vastly most common and important controls in a sub menu (e.g. cut/copy/paste), thus it is an unnecessary extra step to use those important features .. repeated hundreds of times each and every session (yes, I do use the key board short cuts, but still). Could those appear at the top level in the pop-up, please?Often reported problem which doesn't have a good solution, because the current menu is made of the set of things people use often.
d) When there are multiple open projects, switching between projects requires going to the "projects" tab, and double clicking on the desired project "to make it the live project". It would be nice, as with the "target selector" to a have a drop box that lists and allows switching between projects, and so without having to leave the "symbols" etc tabs.This could be done in the similar fashion to the target select dialog, so patches welcome.
e) The symbols tabs "collapse" every time a new (open and already used/"symbolised") file . It would be nice if the symbols list would be preserved (as expanded) when switching between files/tabs and the location of the current s/r/symbol be preserved (i.e. to make it bold for the current procedure of symbol.The symbols browser is going away with the next release (the c/c++ version), at least for people on linux/osx. So it is not too good if you're to used to it.
cacb: What happens if you use gdb from the command line? Can you debug your library? Are you sure you're not stripping the symbols of your library (-s option)?
compiler: Add button to compiler toolbar to show the select target dialog
BACKTRACE:
[1] wxWindowBase::RemoveEventHandler(wxEvtHandler*)
[2] wxKeyBinder::DetachAll()
[3] cbKeyBinder::OnRelease(bool)
[4] cbPlugin::Release(bool)
[5] PluginManager::DetachPlugin(cbPlugin*)
[6] PluginManager::UnloadPlugin(cbPlugin*)
[7] PluginManager::UnloadAllPlugins()
[8] PluginManager::~PluginManager()
[9] PluginManager::~PluginManager()
[10] Manager::Shutdown()
[11] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, wxEvent&) const
[12] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[13] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[14] wxEvtHandler::TryHereOnly(wxEvent&)
[15] wxEvtHandler::DoTryChain(wxEvent&)
[16] wxEvtHandler::ProcessEvent(wxEvent&)
[17] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[18] wxWindowBase::Close(bool)
[19] g_closure_invoke
[20] g_signal_emit_valist
[21] g_signal_emit
[22] gtk_main_do_event
[23] g_main_context_dispatch
[24] g_main_loop_run
[25] gtk_main
[26] wxGUIEventLoop::DoRun()
[27] wxEventLoopBase::Run()
[28] wxAppConsoleBase::MainLoop()
[29] wxEntry(int&, wchar_t**)
[30] __libc_start_mainThanks, I've forgotten to change the tooltip, I've only changed the status bar help message.Quotecompiler: Add button to compiler toolbar to show the select target dialog
Small bug: The tooltip of this button reads "Abort".
Not sure what this does different from the Choice-control next to it...
Thanks, I've forgotten to change the tooltip, I've only changed the status bar help message.
This button is useful for projects with hundreds or thousands of targets (produces by cmake for example).
In these projects you have no chance to use the choice control...
Even if I remove the Main toolbar the remaining is too wide, causing the Code Completion toolbar to become unusable, so regrettably I have to disable Code Completion instead.For the CC's toolbar, you may look at Code::Blocks / Tickets / #303 make code completion's toolbar configurable (https://sourceforge.net/p/codeblocks/tickets/303/) and Code::Blocks / Tickets / #502 resize of code completion toolbar (https://sourceforge.net/p/codeblocks/tickets/502/)
Spelling does not work. The practical use of this version is impossible! hint to solve the problem: - "-funsigned-char"Are these two separate bug reports in two vague sentences or just one?
4) Regarding "open window list/navigation".
CentOS 7 and Fedora 25, 26, 27 and Rawhide packages are available from my copr (see signature).Debian packages are now available again, please test whether the repo works or not (see signature).
Building Debian packages is currently stalled. I don't know if I will start building for Debian again, because it's much work and I do not use Debian since years.
cacb: Can you run cb under gdb and when it crashes to execute "thread apply all bt" command and then paste the output here? Make sure to install the package with the debug symbols.