1. 09 Jan, 2020 1 commit
    • Friedrich W. H. Kossebau's avatar
      kdevplatform: remove About data feature · 381aec18
      Friedrich W. H. Kossebau authored
      With KDevPlatform no longer a stand-alone product, but effectively
      only an internal architecture platform of KDevelop, the About data
      and the About KDevPlatform dialog no longer make sense
      
      Any author information is merged with the one of the KDevelop app,
      which it already almost was a subset of.
      381aec18
  2. 07 Jan, 2020 1 commit
  3. 02 Jan, 2020 1 commit
  4. 01 Nov, 2019 1 commit
  5. 27 Sep, 2019 1 commit
  6. 21 Jul, 2019 1 commit
  7. 17 Jun, 2019 1 commit
  8. 29 Dec, 2018 1 commit
  9. 20 Nov, 2018 1 commit
  10. 10 Sep, 2018 1 commit
  11. 30 Aug, 2018 1 commit
  12. 24 Aug, 2018 1 commit
  13. 21 Aug, 2018 1 commit
  14. 20 Aug, 2018 1 commit
  15. 19 Aug, 2018 1 commit
  16. 18 Aug, 2018 1 commit
  17. 17 Aug, 2018 1 commit
  18. 29 Jul, 2018 2 commits
  19. 22 Jul, 2018 1 commit
  20. 17 May, 2018 1 commit
  21. 21 Nov, 2017 1 commit
  22. 17 Nov, 2017 1 commit
  23. 16 Nov, 2017 5 commits
  24. 04 Nov, 2017 1 commit
  25. 20 Oct, 2017 1 commit
  26. 09 Oct, 2017 1 commit
  27. 01 Oct, 2017 1 commit
    • Friedrich W. H. Kossebau's avatar
      Ensure setting of custom app language is seen on start-up · 5cba8f47
      Friedrich W. H. Kossebau authored
      The custom language setting is read in from the config in a method hooked
      up to the QApp instance creation (see KXMLGUI's kswitchlanguagedialog_p.cpp
      sources), which deploys the custom setting by setting the LANGUAGE env var.
      
      For this to work, the respective init code of KLocalizedString static
      data, which contains the set of languages as read from the env vars,
      needs to be only triggered after the QApp instance creation.
      
      Which includes calling KLocalizedString::setApplicationDomain() only then,
      which this patch cares for.
      5cba8f47
  28. 14 Aug, 2017 1 commit
  29. 13 Jul, 2017 1 commit
  30. 30 May, 2017 1 commit
  31. 15 May, 2017 1 commit
    • Aleix Pol Gonzalez's avatar
      Make it possible to open directories from the command line · b8e426be
      Aleix Pol Gonzalez authored
      Summary:
      When using the terminal, it's sometimes useful to open the project we're in
      with KDevelop. Running `kdevelop .` would do this in this case.
      If kdevelop isn't running then it uses a fresh instance, if it does it tells
      the ones we're using to open the project, just like for files.
      
      Reviewers: #kdevelop, vhanda, mwolff
      
      Reviewed By: #kdevelop, mwolff
      
      Subscribers: mwolff, kfunk, cullmann, zhigalin, kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D5754
      b8e426be
  32. 14 May, 2017 1 commit
    • René J.V. Bertin's avatar
      Don't remove an existing app icon · 2042e4da
      René J.V. Bertin authored
      This corrects commit 0d56bd9a
      which had the effect of removing the embedded application icon
      on systems like Mac and MS Windows where icon themes are typically
      not configured, and QIcon::fromTheme() thus returns an empty QIcon.
      QIcon::fromTheme() should always be called with a valid fallback
      icon, for instance the target icon (QApplication::windowIcon()).
      2042e4da
  33. 12 May, 2017 2 commits
    • Friedrich W. H. Kossebau's avatar
      No longer use QLoggingCategory::setFilterRules() to set default · dbd1139a
      Friedrich W. H. Kossebau authored
      Emables use of qtlogging.ini config files by the user
      (e.g. via kdebugsettings)
      dbd1139a
    • Friedrich W. H. Kossebau's avatar
      Default to disabled debug log on Q_LOGGING_CATEGORY calls · 256c5f4c
      Friedrich W. H. Kossebau authored
      This removes the need to call QLoggingCategory::setFilterRules()
      in the program code to default to disabled debug type log
      without any other settings.
      The latter has disadvantages, as it shadows any settings done
      in qtlogging.ini config files by the user
      (e.g. via kdebugsettings), thus enabling runtime control only
      via QT_LOGGING_CONF/QT_LOGGING_RULES, which is not that
      comfortable with lots of categories.
      
      Also use ECMQtDeclareLoggingCategory for less manual code
      
      While there can be some inconsistency with the default disabled
      log categories by ECMQtDeclareLoggingCategory, which
      switched to QtInfoMsg for ECM 5.26 (when KF5 5.26 has Qt 5.5
      as min dep, which is the Qt version QtInfoMsg was added),
      current KDevPlatform code has Qt 5.4 as minimum version and
      thus also does not use qCInfo, so KDevPlatform behaviour should
      be the same across used Qt versions.
      256c5f4c
  34. 27 Apr, 2017 1 commit