1. 11 Aug, 2019 3 commits
  2. 10 Aug, 2019 1 commit
  3. 08 Aug, 2019 1 commit
  4. 07 Aug, 2019 2 commits
    • Friedrich W. H. Kossebau's avatar
      appdata: add <launchable/> entry · ab22ca65
      Friedrich W. H. Kossebau authored
      Using the pick-session desktop file here, as this keeps the user in
      control what session will be started or allows to create a new.
      The plain desktop file loading randomly the last used session loaded,
      which also could be heavy on resources, might not be wanted at least
      by people with many sessions.
    • David Redondo's avatar
      Fix registry path inside kdevelop-msvc.bat · c702a847
      David Redondo authored
      The company name was changed in craft in 2de26ec4179a18f377736b633f1be7c85ca4a8ee
  5. 05 Aug, 2019 6 commits
  6. 04 Aug, 2019 1 commit
  7. 01 Aug, 2019 1 commit
  8. 31 Jul, 2019 1 commit
  9. 30 Jul, 2019 1 commit
  10. 28 Jul, 2019 1 commit
  11. 27 Jul, 2019 1 commit
  12. 26 Jul, 2019 2 commits
  13. 25 Jul, 2019 6 commits
  14. 24 Jul, 2019 2 commits
  15. 23 Jul, 2019 2 commits
  16. 22 Jul, 2019 3 commits
  17. 21 Jul, 2019 6 commits
    • Friedrich W. H. Kossebau's avatar
    • Friedrich W. H. Kossebau's avatar
      appimage: build kdeevelop 5.4 · 8a263a0e
      Friedrich W. H. Kossebau authored
    • Friedrich W. H. Kossebau's avatar
      Set version number to 5.3.80 · 0424e047
      Friedrich W. H. Kossebau authored
    • 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.
    • 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