Author Topic: The 20 September 2017 build (11176) is out.  (Read 3101 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5016
The 20 September 2017 build (11176) is out.
« on: September 21, 2017, 09:14:05 am »
Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works.

A link to the unicode windows wxWidget dll for Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw28u_gcc_cb_wx2812_gcc510-TDM-2.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/mingwm10_gcc510-TDM.7z

The 20 September 2017 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2017/CB_20170920_rev11176_win32.7z
  - Linux :
   none

The current SDK version is : 1.31.0

Resolved Fixed:

  • UI: Fix redraw problem on ubuntu because freeze/thaw are used in a wrong way
  • ScriptedWizard YWX additions (GetWizardScriptFolder, FillContainerWithSelectCompilers,AppendContainerWithSelectCompilers,FillContainerWith
  • wxSmith: Add wxSpinCtrl alignment styles
  • SDK resources - PowerShell script lexer xml and sample
  • CC: fix an issue that Code Completion list got hidden after shown up
  • UI: Do not loose changes when clicking twice the same target in ProjectOption dialog (ticket #547, thanks homertp)
  • wx3: Memory dump window has wrong proportion on windows (ticket #557, thanks bluehazzard)
  • debugger: Start the removal of squirrel based pretty printers
  • debugger: Remove stl-view gdb script file because it is not used anymore
  • debugger: Remove the config option to enable/disable script watches
  • debugger: Build system cleanup after the removal of scripted watches
  • compiler: Improve clang log parsing
  • compiler: Add button to compiler toolbar to show the select target dialog
  • autotools: Fix compilation using autotools on OSX
  • autotools: Add OSX bundle making support (ticket #562, thanks Dave Murphy)
  • osx: Fix blurryness when making a bundle
  • OSX: Move the wizard files to the correct folder when making bundle

Regressions/Confirmed/Annoying/Common bugs:



    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 10277
    Re: The 20 September 2017 build (11176) is out.
    « Reply #1 on: September 21, 2017, 08:34:46 pm »
    I have the intention to make a final release based on this night build.
    Please test it and report as many problems, so we can have a solid release.

    Thanks to all.
    <debugger plugin maintainer>
    (most of the time I ignore long posts)
    [strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

    Offline Xaviou

    • Regular
    • ***
    • Posts: 250
      • X@v's wxStuff
    Re: The 20 September 2017 build (11176) is out.
    « Reply #2 on: September 21, 2017, 09:30:12 pm »
    Hi
    I have the intention to make a final release based on this night build.
    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) ?

    Regards
    Xav'
    The french wxWidgets site : http://www.wxdev.fr
    My wxWidgets's stuff : http://wxstuff.xaviou.fr/

    Offline Xaviou

    • Regular
    • ***
    • Posts: 250
      • X@v's wxStuff
    Re: The 20 September 2017 build (11176) is out.
    « Reply #3 on: September 21, 2017, 10:04:56 pm »
    Here is a strange behavior I've noticed many times on Windows.

    When a file has mixed tabulations chars for indentation, it is sometimes badly rendered by Code::Blocks.

    It is a little bit hard to reproduce as it doesn't happen each time a file has tabulations inconsistencies.

    You can try doing the following (it has just worked for me) :
    • Open a class header file
    • Replace all tabulations by 4 spaces
    • save the file
    • open the file in another text editor, and replace the first 4 spaces indentation by a tab char
    • save and re-open in Code::Blocks
    • the modified line should appear as if it was having 2 tabs

    Attached are screenshots of the same file opened in Code::Blocks and in another text editor (I've enabled the display of whitespaces to see the difference)

    And then, when a file with this problem is opened in Code::Blocks, if you want to make indents consistents, it won't be done correctly.
    I've tried "Edit" => "Editor tweaks" => "Use Tab Character"
    and "Edit" => "Editor tweaks" => "Make Indents Consistent"

    All lines are correctly indented with tab character but the line #15 still have 4 spaces (and the tab chars are represented as 8 spaces each)

    Regards
    Xav'
    « Last Edit: September 21, 2017, 10:10:52 pm by Xaviou »
    The french wxWidgets site : http://www.wxdev.fr
    My wxWidgets's stuff : http://wxstuff.xaviou.fr/

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 10277
    Re: The 20 September 2017 build (11176) is out.
    « Reply #4 on: September 21, 2017, 10:35:38 pm »
    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.
    I'm not sure that it'll be possible to fix many OSX problems at the moment, but if there is something that is really bad I could look at it.
    <debugger plugin maintainer>
    (most of the time I ignore long posts)
    [strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 10277
    Re: The 20 September 2017 build (11176) is out.
    « Reply #5 on: September 21, 2017, 11:01:18 pm »
    For the editor problem please post it in another topic or even in a ticket on sf.net.
    <debugger plugin maintainer>
    (most of the time I ignore long posts)
    [strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

    Offline jens

    • Administrator
    • Lives here!
    • *****
    • Posts: 7207
      • Jens' unofficial debian-repository for the Code::Blocks - IDE
    Re: The 20 September 2017 build (11176) is out.
    « Reply #6 on: September 21, 2017, 11:57:47 pm »
    CentOS 7 and Fedora 25, 26, 27 and Rawhide packages are available from my copr (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.

    Offline DrOli

    • Multiple posting newcomer
    • *
    • Posts: 40
    Hi

    Tried to provide bug reports and feature requests, but the redirection to the derlios.de cite is not particularly useful ... no idea how to actually get to the ticket page, all it shows is "Dating", "Gaming" and other such consumer matters.

    I can repost these separately later if you like once the "delrios" matter is corrected, but just so you have the key bits before releasing the new CB:

    Under WinXP64/Win764

    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 feature works with c/cpp files.

    3) Some "feature requests":

    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)

    b) Please add a "view windows/tabs" item to the toolbar that allows reviewing and navigating directly to open files/tabs.

    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?

    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.

    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.

    ... these are relatively minor things, and CB is a great product.

    Offline stahta01

    • Lives here!
    • ****
    • Posts: 5943
      • My Best Post
    Re: The 20 September 2017 build (11176) is out.
    « Reply #8 on: September 29, 2017, 02:39:44 pm »
    @DrOli: Please post the link that tells you to go to the derlios.de or berlios.de website; it has NOT been the proper website for years.

    Tim S.
    C Programmer working to learn more about C++ and Git.
    On Windows 7 64 bit and Windows 10 32 bit.
    On Debian Testing, compiling CB Trunk against wxWidgets 3.0.2.
    --
    When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

    Offline BlueHazzard

    • Lives here!
    • ****
    • Posts: 1519
    Re: The 20 September 2017 build (11176) is out.
    « Reply #9 on: September 29, 2017, 03:32:20 pm »
    Quote
    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

    Quote
    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

    Quote
    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...

    Offline cacb

    • Regular
    • ***
    • Posts: 365
    Re: The 20 September 2017 build (11176) is out. - Can't access bug/feature ticke
    « Reply #10 on: September 29, 2017, 04:22:07 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.

    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.
    « Last Edit: September 29, 2017, 11:37:34 pm by cacb »

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 10277
    Re: The 20 September 2017 build (11176) is out. - Can't access bug/feature ticke
    « Reply #11 on: September 29, 2017, 08:15:26 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.

    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.

    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
    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.

    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.
    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.

    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.

    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!
    <debugger plugin maintainer>
    (most of the time I ignore long posts)
    [strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

    Offline cacb

    • Regular
    • ***
    • Posts: 365
    Re: The 20 September 2017 build (11176) is out.
    « Reply #12 on: September 29, 2017, 10:30:08 pm »
    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?

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 10277
    Re: The 20 September 2017 build (11176) is out.
    « Reply #13 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)?
    <debugger plugin maintainer>
    (most of the time I ignore long posts)
    [strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

    Offline cacb

    • Regular
    • ***
    • Posts: 365
    Re: The 20 September 2017 build (11176) is out.
    « Reply #14 on: September 29, 2017, 10:56:20 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)?

    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!
    « Last Edit: September 29, 2017, 11:12:19 pm by cacb »

    Offline cacb

    • Regular
    • ***
    • Posts: 365
    Re: The 20 September 2017 build (11176) is out.
    « Reply #15 on: September 29, 2017, 11:33:02 pm »
    Quote
    compiler: 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...

    Offline cacb

    • Regular
    • ***
    • Posts: 365
    Re: The 20 September 2017 build (11176) is out.
    « Reply #16 on: September 29, 2017, 11:50:27 pm »
    I got a traceback when exiting C::B using the top right system 'X' button on the C::B main window. On trying to reproduce it, the traceback does not show. Seems like an intermittent problem.

    Code: [Select]
    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_main

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 10277
    Re: The 20 September 2017 build (11176) is out.
    « Reply #17 on: September 30, 2017, 12:36:19 am »
    Quote
    compiler: 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...
    <debugger plugin maintainer>
    (most of the time I ignore long posts)
    [strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

    Offline cacb

    • Regular
    • ***
    • Posts: 365
    Re: The 20 September 2017 build (11176) is out.
    « Reply #18 on: September 30, 2017, 01:16:32 pm »
    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...

    Ok, understand, fair enough. I never have such projects...

    Somehow semi-related comment: When adding buttons to toolbars, you eat up toolbar space. I would like to to have the following toolbars in one row only (because 2 rows use far too much space):  Main, Compiler, IncrementalSearch, Debugger, Code Completion

    This is currently not possible with KDE even on my 24inch screen. 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. If it was possible to hide some never used buttons (I use < 50% of them) in the existing toolbars they would fit easily.

    Anyway, this version seems very good!

    Offline ollydbg

    • Developer
    • Lives here!
    • *****
    • Posts: 4970
    • OpenCV and Robotics
      • Chinese OpenCV forum moderator
    Re: The 20 September 2017 build (11176) is out.
    « Reply #19 on: September 30, 2017, 03:25:17 pm »
    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 and Code::Blocks / Tickets / #502 resize of code completion toolbar
    If some piece of memory should be reused, turn them to variables (or const variables).
    If some piece of operations should be reused, turn them to functions.
    If they happened together, then turn them to classes.

    Offline Khram

    • Single posting newcomer
    • *
    • Posts: 5
      • ShipDesign
    Re: The 20 September 2017 build (11176) is out.
    « Reply #20 on: October 01, 2017, 11:29:13 am »
    Spelling does not work!!!. The practical use of this version is impossible! hint to solve the problem: - "-funsigned-char"


    I have the intention to make a final release based on this night build.
    Please test it and report as many problems, so we can have a solid release.

    Thanks to all.
    « Last Edit: October 01, 2017, 12:15:26 pm by Khram »
    C++ & Fortran in MinGW-GCC-4.3.3 & Equation-GCC-6.3.0 with CB 13.12-9958

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 10277
    Re: The 20 September 2017 build (11176) is out.
    « Reply #21 on: October 01, 2017, 11:41:23 am »
    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?

    The spelling problem has a topic! Post the details how to reproduce the problem there and we'll fix the problem. If you don't do this we could not do anything about your problem...
    Next time I'll report similar post in nightly topic to moderator as trolling.
    <debugger plugin maintainer>
    (most of the time I ignore long posts)
    [strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

    Offline DrOli

    • Multiple posting newcomer
    • *
    • Posts: 40
    Re: The 20 September 2017 build (11176) is out.
    « Reply #22 on: October 01, 2017, 03:07:53 pm »
    Dear Sirs and oBFusCATed

    Regarding the various kind and prompt response to my (DrOli) posts (the high priority items ended up at the bottom):

    1) the Bug report issue Re berlios.de is on the "how to use a nightly build" here (http://forums.codeblocks.org/index.php?topic=3232.0)  in para 6.  This is also at the "top level" and highlighted item on this (main CB blog) page (http://forums.codeblocks.org/index.php/board,20.0.html)

    If those links are "defunct" ... please be so kind as to post instructions/links to your preference.

    As promised, I would be happy to re-file these various items into individual bug/feature reports, once provided with instructions.


    2) Re "target" Drop Down.  Ok, I see with the nightly there is a new "abort" button (odd name), which does launch a dialogue with the full list of targets. 

    That's is helpful thank you, but surely having the drop down itself show up to 8 - 10 lines can't be too difficult, and is much more convenient compared to the additional steps of a dialogue.  Not sure how CB/wsx handles such, but any GUI I've used often has a explicit property/switch to indicate number of items in DropDown (or "max, or etc) ... perhaps that is why I though it might be something quick/easy.

    3) Regarding the SVN crashes ... yes, I am sorry that I can't provide some details to permit reproducibility.  As I had noted, if I could, I would.  For the moment, all I can say is, it happens almost every session with the SVN's (including 11176).  It seems to occur when there are multiple projects open, there is switching back/fro, and though it sometimes crashes "mid stream", most of crashes (most every session). occur at shut down.

    ALSO, something odd, the SVN's are always asking for my choice of compiler on launch, where as 16.1 does not.  My compilers are well defined so not sure why the nightly's get confused (particularly if they rely on the same "config" etc).

    4) Regarding "open window list/navigation".  Thanks for the Atl-g heads up ... Alas, that is not what is required.  The objective is for, like with almost all normal apps, to have a Toolbar/View or something that provides a drop-down of the "OPEN file" (i.e. those in the editor with tabs etc.) ... as opposed to Alt-g, which seems to list all the files in the project (open or not).


    5) Regarding "right click pup up menu":  There is almost NOTHING in the top level that I EVER use, save for "watch" sometimes", almost exclusively what I use is in "copy/paste" sub menu (though the inconvenience forces my to use key stroke, an improvement, but still a kludge)

    "Simplifying" it by disabling plug-ins is a bit tricky.  Essentially, I only need one plug in, but for that work, I have to enable all manner of things I don't need (and in some cases hate, like code completion)

    You seem to say that "most" like the layout as it is ... that may be true, but I find that a little hard to believe.  Regardless, perhaps you could give the user a CHOICE for the "default pup up", perhaps as part of the "settings/env".  You could have the huge cluttered obstructive one for the masochists, and a clean easy to use efficient one for the rest of us :-). 

    In an app I wrote, the user had a "toggle" directly on the pop-up to change "format/content".  CB need not be that fancy ... just a thought.


    6) Fortran/debug link.  No idea why it used to work (at least partially) but very clearly has stopped working almost entirely at least since GCC5.x

    I don't know anything about CodeBlock "innards" or wxs etc.  So not sure how I could contribute, but if you point me in the right direction (and perhaps offer a little "hand holding", I'll give it go.  I would need at least some list of files and "mechanisms" to understand how that operates.

    Though, and perhaps a sign of my ignorance, I don't understand why it works fir .c, .cc, .cpp file, and not .f90 etc files.  It is clear the compiler reports back the line numbers of the offending lines (I then use Ctrl g to go to those lines, with Fortran).  Why CB can't make the connection between the compiler's file/line report and provide the linkage (when it can for c etc) seems odd.

    If it helps, you can send info directly to me: droli [theatsymbol] thebajors <thedotsymbol> com to get me started to see if I could produce a patch or whatever (remember, hand holding may be required, I am a "math geek" not an "IT geek"/developer. :-)


    7) Finally, and a bit frightening, you seem to be saying that the symbol explorer will be removed.  Is that for sure?  I desperately rely on that, and especially the Fortran FSymbol variant (which I understand is a plug-in written by one of the users) ... what would it take to keep that going ... this would be HIGH priority for me.

    If it helps, you can send info directly to me: droli [theatsymbol] thebajors <thedotsymbol> com to get me started to see if I could produce a patch or whatever (remember, hand holding may be required, I am a "math geek" not an "IT geek"/developer. :-)


    Many thanks

    DrO



    Offline blauzahn

    • Multiple posting newcomer
    • *
    • Posts: 68
    Re: The 20 September 2017 build (11176) is out.
    « Reply #23 on: October 01, 2017, 03:39:20 pm »
    @DrOli

    Quote
    4) Regarding "open window list/navigation". 

    a) menu: view | open files list
    or
    b) menu: settings | environment | notebooks appearance | use drop-down tab list

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 10277
    Re: The 20 September 2017 build (11176) is out.
    « Reply #24 on: October 01, 2017, 04:05:04 pm »
    @DrOli:

    1. Bugs and feature requests could be posted here: https://sourceforge.net/p/codeblocks/tickets/ Please search before posting!!!
    2. There is no place for another choice/drop down control in the compiler toolbar, so if we do it, it will be done as a button or as a submenu in the project menu. I have no idea what you meant with the max items statement...
    3. Can you disable code completion and/or the symbol browser and see if these go away. Does they happen when you edit c/cpp projects or only for fortran projects?
    3.1. Are you able to make CB close correctly (without crashing) at least once? Also make sure the default.conf in %APPDATA% folder is writeable.
    5. You're one sample, so your opinion is recorded. I use more than one of these and I'd never use copy/cut/paste, so I'm another sample... Configurable context menus and toolbars is on my todo, but it is really low priority... Patches welcome, but they would required a lot of rework of the menu/keybind system. I guess, I can easily make a global  control that disables the items produced by plugins. This might be something easy to do.
    6. Are you talking about the detection of errors/warnings? I've given you suggestion how to fix those.
    7. Yes the one for c/c++ is already disabled for wx3.x builds. The windows builds are still done with wx2.8, but when we switch them the symbol browser will gone until someone finds the time to reimplement it. I'm not using it much so the chances of me doing it are very low. The fsymbols tab is part of the fortran plugin, so I don't have control over it. But if it is implemented in the same fashion as the c/c++ one it will cause a lot of crashes when cb is build for wx3.x, so it will have to be redone or disabled, too.
    <debugger plugin maintainer>
    (most of the time I ignore long posts)
    [strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

    Offline jens

    • Administrator
    • Lives here!
    • *****
    • Posts: 7207
      • Jens' unofficial debian-repository for the Code::Blocks - IDE
    Re: The 20 September 2017 build (11176) is out.
    « Reply #25 on: October 01, 2017, 05:42:22 pm »
    CentOS 7 and Fedora 25, 26, 27 and Rawhide packages are available from my copr (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.
    Debian packages are now available again, please test whether the repo works or not (see signature).
    I do not use Debian myself since years.
    Builds only happen for the convenience of our users.

    Offline cacb

    • Regular
    • ***
    • Posts: 365
    Re: The 20 September 2017 build (11176) is out.
    « Reply #26 on: October 01, 2017, 09:29:46 pm »
    For the record, these builds appear to be running smoothly with no serious issues:

    under Kubuntu 17.04
    svn build rev 11179 (2017-09-28 21:32:47) gcc 6.3.0 Linux/unicode - 64 bit
    self build from https://github.com/obfuscated/codeblocks_sf

    under Win7 64bit
    svn build rev 11176 (2017-09-18 08:43:00) gcc 5.1.0 Windows/unicode - 32 bit
    Downloaded Nightly binary from this thread

    Looking quite good.

    Offline cacb

    • Regular
    • ***
    • Posts: 365
    Re: The 20 September 2017 build (11176) is out.
    « Reply #27 on: October 03, 2017, 08:34:14 pm »
    crash during editing of source file. Adding parameter to function call. XML attached.

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 10277
    Re: The 20 September 2017 build (11176) is out.
    « Reply #28 on: October 03, 2017, 08:41:25 pm »
    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.
    <debugger plugin maintainer>
    (most of the time I ignore long posts)
    [strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

    Offline cacb

    • Regular
    • ***
    • Posts: 365
    Re: The 20 September 2017 build (11176) is out.
    « Reply #29 on: October 06, 2017, 11:40:46 am »
    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.

    I have not been able to reproduce the problem (which was real enough).

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 10277
    Re: The 20 September 2017 build (11176) is out.
    « Reply #30 on: October 06, 2017, 08:33:24 pm »
    I run codeblocks under gdb all the time. Please do it for a while and just wait. It happened more then once it will happen again.
    <debugger plugin maintainer>
    (most of the time I ignore long posts)
    [strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]