User forums > Nightly builds
The 20 September 2017 build (11176) is out.
cacb:
--- Quote from: DrOli on September 29, 2017, 01:44:10 pm ---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.
--- End quote ---
I agree with this. The Right-Click pop-up has too many things in it and the most important items (cut/copy/paste) are in an inconvenient submenu. Compare e.g. with Notepad++ which I think is more optimal.
Things I think could be modified in the pop-up menu. These are just my quick personal opinions
- "toggle breakpoint" could be removed or pushed further down, it has a shortcut and is in the Debug menu anyway
- "Bookmarks" I never use, could be removed
- "Format use Astyle" seems like a special feature (I never use it). Move to main Edit menu?
- "Browse Tracker". Not sure what it is doing. Could be removed
- "Search at "Black Duck...". Why is this feature here?
- "Locate in CodeBlocks" . Not sure what it does
- "Add ToDo Item" ... I never use it
- "Split View". feature I almost never use
In short, I think the menu is too cluttered with secondary things, while the most important (cut/copy/paste) suffers.
Just my opinion.
oBFusCATed:
--- Quote from: DrOli on September 29, 2017, 01:44:10 pm ---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.
--- End quote ---
We need a reliable way to reproduce this or we need backtraces (or crashes reports, codeblocks.xml, files). Without this information we could not do much.
--- Quote from: DrOli on September 29, 2017, 01:44:10 pm ---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.
--- End quote ---
The output is parsed using regular expressions. They could be edited in the advanced compiler options dialog or in
the options_gfortran.xml. Most of the users and developers of cb are c/c++ devs, so we need help with the support
for other languages.
If you provide patches, I'll happily review and apply them.
--- Quote from: DrOli on September 29, 2017, 01:44:10 pm ---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?
--- End quote ---
Often reported problem which doesn't have a good solution, because the current menu is made of the set of things people use often.
I'll move some of the menu items around and test with myself if migrating to the new configuration is too annoying or I can get used to it.
If the experiment is successful, then I'll make a change for some night build to see how this change is received by more people.
This could be improved if you disable some of the plugins you don't use.
--- Quote from: DrOli on September 29, 2017, 01:44:10 pm ---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.
--- End quote ---
This could be done in the similar fashion to the target select dialog, so patches welcome.
--- Quote from: DrOli on September 29, 2017, 01:44:10 pm ---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.
--- End quote ---
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.
p.s. if you want to turn this in a discussion about the context menu, please start new topic! This one is for bug reports!
cacb:
I have rebuilt from https://github.com/obfuscated/codeblocks_sf under Kubuntu 17.04
It resulted in build 11179. The build is fine, but I experience problems with the debugger (also seen before in build 11019).
Problem description: I have a console program using a .so library. The program runs fine, but the debugger only works for the main project, not for the code in the .so library. Breakpoints are ignored and I cannot step into the code in the .so library. Both projects are built with debug options.
Is this a known problem?
oBFusCATed:
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)?
cacb:
--- Quote from: oBFusCATed on September 29, 2017, 10:40:08 pm ---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)?
--- End quote ---
There should be no symbol stripping going on, I have used this setup for a long time. I also checked the project file, but could not see anything like that.
on gdb from the command line, I can try. But I have never used gdb from the command line before so I will need to figure it out, how to set breakpoints and step etc.
EDIT: I was wrong, sorry. Indeed there was a -s option causing symbol stripping! Now the debugger works as expected, thanks a lot!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version