1. 05 Aug, 2019 6 commits
  2. 04 Aug, 2019 1 commit
  3. 01 Aug, 2019 1 commit
  4. 31 Jul, 2019 1 commit
  5. 30 Jul, 2019 1 commit
  6. 28 Jul, 2019 1 commit
  7. 27 Jul, 2019 1 commit
  8. 26 Jul, 2019 2 commits
  9. 25 Jul, 2019 6 commits
  10. 24 Jul, 2019 2 commits
  11. 23 Jul, 2019 2 commits
  12. 22 Jul, 2019 3 commits
  13. 21 Jul, 2019 7 commits
    • Friedrich W. H. Kossebau's avatar
    • Friedrich W. H. Kossebau's avatar
      appimage: build kdeevelop 5.4 · 8a263a0e
      Friedrich W. H. Kossebau authored
      8a263a0e
    • Friedrich W. H. Kossebau's avatar
      Set version number to 5.3.80 · 0424e047
      Friedrich W. H. Kossebau authored
      0424e047
    • Thomas Schöps's avatar
      Contextbrowser: Minor improvement to tooltip showing behavior · c1e8604d
      Thomas Schöps authored
      The aim is to decide properly when the currently shown tooltip needs to be updated and when it doesn't, based on the problems and declaration that are currently being displayed in the tooltip (stored in m_currentToolTipProblems and m_currentToolTipDeclaration), and the new problems and declaration that are under the cursor now (in problems and decl).
      
      Old line 612: The old version always keeps showing the current tooltip if the problems haven't changed and there is no declaration. But there might have been a declaration before, and in this case this declaration's info would incorrectly be continued to be shown. The new version fixes that by removing the "!decl" part and thus always also testing for existence/equality of the declaration.
      
      Old lines 616 .. 648: In case there is no declaration (!decl), the old version does not remember this in m_currentToolTipDeclaration at the top of this block. But the problems are always remembered. In the new version, the logic is clarified: If either there are problems or there is a declaration, then the current state concerning both is remembered in m_currentToolTipProblems and m_currentToolTipDeclaration, and corresponding widgets will be created in the code below. If not, m_currentToolTipProblems and m_currentToolTipDeclaration aren't touched yet, since there is additional code below that handles additional cases.
      
      New lines 665 .. 669: Here the check is extended to also test for equality of the declaration, i.e., for no declaration, since this case is about to show a problems-only tooltip.
      
      New line 672: Here the code is extended to remember the current state of both the problems and the declaration in the tooltip.
      
      New line 684: If the execution reaches this point, neither a problem nor a declaration has been found that shall be displayed. So, instead of returning nullptr and thus continuing to show whatever tooltip is currently being shown, the correct behavior should be to stop showing the tooltip if there is any.
      c1e8604d
    • Thomas Schöps's avatar
    • Thomas Schöps's avatar
      CMake plugin: Also show an error message if the CMake configuration becomes... · 27125715
      Thomas Schöps authored
      CMake plugin: Also show an error message if the CMake configuration becomes invalid due to a change, and add an instruction to reload the project manually
      27125715
    • Thomas Schöps's avatar
      1ee9f8d5
  14. 20 Jul, 2019 4 commits
    • Ben Wagner's avatar
      Add working directory to clang parser. · ad7ea392
      Ben Wagner authored
      Summary:
      This sets the working directory of the clang parser similarly to the way
      the build directory is passed to the builder. This allows the parser to
      correctly resolve any relative paths in the extra build arguments. This
      means relative paths are resolved relative to the build directory (as
      they would be resolved by a builder).
      
      Test Plan: In the current test setup it doesn't seem the TestProject allows a TestBuildSystemManager, so it seems like quite a bit of work to create a test for this. (As a result I assume IBuildSystemManager integration isn't well tested in general right now.) If this needs a test, let me know if adding a TestBuildSystemManager is the right way to go.
      
      Reviewers: #kdevelop, aaronpuchert
      
      Reviewed By: aaronpuchert
      
      Subscribers: aaronpuchert, kdevelop-devel
      
      Tags: #kdevelop
      
      Differential Revision: https://phabricator.kde.org/D22197
      ad7ea392
    • Daniel Mensinger's avatar
      Fixed typo · 5f9fcc13
      Daniel Mensinger authored
      5f9fcc13
    • Daniel Mensinger's avatar
      58e6d4c6
    • Daniel Mensinger's avatar
      88861caf
  15. 19 Jul, 2019 2 commits