1. 13 Jul, 2017 1 commit
  2. 30 May, 2017 1 commit
  3. 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
  4. 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
  5. 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
  6. 27 Apr, 2017 3 commits
  7. 07 Apr, 2017 1 commit
  8. 06 Apr, 2017 1 commit
  9. 01 Apr, 2017 1 commit
  10. 17 Mar, 2017 2 commits
  11. 23 Feb, 2017 1 commit
  12. 14 Feb, 2017 1 commit
    • Friedrich W. H. Kossebau's avatar
      Standardize on "Executable" in UI & API, do not mix with "Binary" · 691f9c46
      Friedrich W. H. Kossebau authored
      Summary:
      For UI:
      * KDevelop supports both scripting and compiled languages,
        so e.g. debugging target can be non-binary
      * external tools might be known as binary-only, but sometimes they
        are inside wrapper scripts and no place really requires a compiled binary
      * consistent terms help users & also translators
      
      For API/variable names:
      * "executable" matches API of Qt
      * consistent with UI language
      
      Config storage keys not touched for now, might need more thinking.
      
      Depends on D4592
      
      Reviewers: #kdevelop, apol
      
      Reviewed By: #kdevelop, apol
      
      Subscribers: flherne, kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D4593
      691f9c46
  13. 12 Jan, 2017 6 commits
  14. 11 Jan, 2017 1 commit
  15. 08 Jan, 2017 1 commit
  16. 30 Dec, 2016 1 commit
  17. 17 Oct, 2016 1 commit
  18. 16 Sep, 2016 1 commit
  19. 14 Sep, 2016 1 commit
  20. 09 Sep, 2016 1 commit
  21. 08 Sep, 2016 3 commits
    • Anton Anikin's avatar
      Fix KDevelop crashes when trying to debug from command-line · 449d55cf
      Anton Anikin authored
      Fixes the crash in KDE bug #367837 that is caused by starting
      debugging session from command line:
      
      kdevelop -d gdb dolphin
      
      This caused to ASSERT: QFile::exists(). Current version fix it
      by searching full paths for such binaries.
      
      BUG:367837
      FIXED-IN: 5.0.1
      (cherry picked from commit b386fb1c)
      449d55cf
    • Anton Anikin's avatar
      Fix KDevelop crashes when trying to debug from command-line · b386fb1c
      Anton Anikin authored
      Fixes the crash in KDE bug #367837 that is caused by starting
      debugging session from command line:
      
      kdevelop -d gdb dolphin
      
      This caused to ASSERT: QFile::exists(). Current version fix it
      by searching full paths for such binaries.
      
      BUG:367837
      b386fb1c
    • Kevin Funk's avatar
      Avoid crash in case plugins are missing · 24871784
      Kevin Funk authored
      ASAN:DEADLYSIGNAL
      =================================================================
      ==24138==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000
      (pc 0x00000053ab14 bp 0x7ffee4565c30 sp 0x7ffee4565820 T0)
          #0 0x53ab13 in KDevelopApplication::saveState(QSessionManager&)
      /home/kfunk/devel/src/kf5/kdevelop-stable/app/main.cpp:162:41
          #1 0x53c82b in QtPrivate::FunctorCall<QtPrivate::IndexesList<0>,
      QtPrivate::List<QSessionManager&>, void, void
      (KDevelopApplication::*)(QSessionManager&)>::call(void
      (KDevelopApplication::*)(QSessionManager&), KDevelopApplication*,
      void**)
      /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:501:13
          #2 0x53c35d in void QtPrivate::FunctionPointer<void
      (KDevelopApplication::*)(QSessionManager&)>::call<QtPrivate::List<QSessionManager&>,
      void>(void (KDevelopApplication::*)(QSessionManager&),
      KDevelopApplication*, void**)
      /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:520:13
          #3 0x53bd4f in QtPrivate::QSlotObject<void
      (KDevelopApplication::*)(QSessionManager&),
      QtPrivate::List<QSessionManager&>, void>::impl(int,
      QtPrivate::QSlotObjectBase*, QObject*, void**, bool*)
      /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject_impl.h:143:17
          #4 0x7fba0e2e8a95 in QtPrivate::QSlotObjectBase::call(QObject*,
      void**)
      /home/kfunk/devel/build/qt5/qtbase/src/corelib/../../include/QtCore/../../../../../src/qt5/qtbase/src/corelib/kernel/qobject_impl.h:101
          #5 0x7fba0e2e8a95 in QMetaObject::activate(QObject*, int, int,
      void**)
      /home/kfunk/devel/src/qt5/qtbase/src/corelib/kernel/qobject.cpp:3723
          #6 0x7fba0e605e54 in
      QGuiApplication::saveStateRequest(QSessionManager&)
      /home/kfunk/devel/build/qt5/qtbase/src/gui/.moc/moc_qguiapplication.cpp:432
          #7 0x7fba0e607fda in QGuiApplicationPrivate::saveState()
      /home/kfunk/devel/src/qt5/qtbase/src/gui/kernel/qguiapplication.cpp:3377
          #8 0x7fb9f3f0dcdc in sm_performSaveYourself(QXcbSessionManager*)
      /home/kfunk/devel/src/qt5/qtbase/src/plugins/platforms/xcb/qxcbsessionmanager.cpp:243
          #9 0x7fb9f3f0e083 in sm_saveYourselfCallback(_SmcConn*, void*, int,
      int, int, int)
      /home/kfunk/devel/src/qt5/qtbase/src/plugins/platforms/xcb/qxcbsessionmanager.cpp:178
          #10 0x7fb9f3888b27 in _SmcProcessMessage
      (/usr/lib/x86_64-linux-gnu/libSM.so.6+0x4b27)
          #11 0x7fb9f367a166 in IceProcessMessages
      (/usr/lib/x86_64-linux-gnu/libICE.so.6+0x10166)
          #12 0x7fba0e2e8728 in QMetaObject::activate(QObject*, int, int,
      void**)
      /home/kfunk/devel/src/qt5/qtbase/src/corelib/kernel/qobject.cpp:3740
          #13 0x7fba0e3613dd in QSocketNotifier::activated(int,
      QSocketNotifier::QPrivateSignal)
      /home/kfunk/devel/build/qt5/qtbase/src/corelib/.moc/moc_qsocketnotifier.cpp:135
          #14 0x7fba0e2f4cba in QSocketNotifier::event(QEvent*)
      /home/kfunk/devel/src/qt5/qtbase/src/corelib/kernel/qsocketnotifier.cpp:266
          #15 0x7fba0ebc1eeb in QApplicationPrivate::notify_helper(QObject*,
      QEvent*)
      /home/kfunk/devel/src/qt5/qtbase/src/widgets/kernel/qapplication.cpp:3741
          #16 0x7fba0ebc98e5 in QApplication::notify(QObject*, QEvent*)
      /home/kfunk/devel/src/qt5/qtbase/src/widgets/kernel/qapplication.cpp:3498
          #17 0x7fba0e2bd9a7 in QCoreApplication::notifyInternal2(QObject*,
      QEvent*)
      /home/kfunk/devel/src/qt5/qtbase/src/corelib/kernel/qcoreapplication.cpp:988
          #18 0x7fba0e3118cc in QCoreApplication::sendEvent(QObject*, QEvent*)
      /home/kfunk/devel/build/qt5/qtbase/src/corelib/../../include/QtCore/../../../../../src/qt5/qtbase/src/corelib/kernel/qcoreapplication.h:231
          #19 0x7fba0e3118cc in socketNotifierSourceDispatch(_GSource*, int
      (*)(void*), void*)
      /home/kfunk/devel/src/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:106
          #20 0x7fba00faa1a6 in g_main_context_dispatch
      (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x4a1a6)
          #21 0x7fba00faa3ff  (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x4a3ff)
          #22 0x7fba00faa4ab in g_main_context_iteration
      (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x4a4ab)
          #23 0x7fba0e31140e in
      QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
      /home/kfunk/devel/src/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:423
          #24 0x7fba0e2bb999 in
      QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
      /home/kfunk/devel/src/qt5/qtbase/src/corelib/kernel/qeventloop.cpp:212
          #25 0x7fba0edab6b6 in QDialog::exec()
      /home/kfunk/devel/src/qt5/qtbase/src/widgets/dialogs/qdialog.cpp:527
          #26 0x7fba0edcd33c in showNewMessageBox(QWidget*, QMessageBox::Icon,
      QString const&, QString const&, QFlags<QMessageBox::StandardButton>,
      QMessageBox::StandardButton) [clone .constprop.36]
      /home/kfunk/devel/src/qt5/qtbase/src/widgets/dialogs/qmessagebox.cpp:1585
          #27 0x7fba147a7079 in QMessageBox::critical(QWidget*, QString
      const&, QString const&, QMessageBox::StandardButton,
      QMessageBox::StandardButton)
      /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qmessagebox.h:262:14
          #28 0x7fba14792105 in
      KDevelop::CorePrivate::initialize(KDevelop::Core::Setup, QString)
      /home/kfunk/devel/src/kf5/kdevplatform-stable/shell/core.cpp:158:13
      24871784
  22. 06 Sep, 2016 1 commit
  23. 22 Aug, 2016 1 commit
  24. 14 Jul, 2016 3 commits
  25. 17 Jun, 2016 1 commit
  26. 16 Jun, 2016 1 commit
    • Kevin Funk's avatar
      Drop splash screen · de5b4080
      Kevin Funk authored
      Summary:
      KDevelop 5 starts significantly faster with all the changes in the
      plugin loading mechanisms. I've also been able to reduce start up time
      of the welcome page plugin significantly lately. Still having a splash
      screen seems old-fashioned, plus adds even more delay to the startup.
      
      Thus finally want to kill it.
      
      More reasons for removing the splash:
      * Delays startup unnecessarily
      * The splash screen is still broken in some configurations:
        Bug: ~10 px border on the right for instance (not going to fix it)
      * It's 2016, splash screens are kind of out of fashion.
      
      See discussion at:
        https://mail.kde.org/pipermail/kdevelop-devel/2016-February/053120.html
      
      Subscribers: kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D1912
      de5b4080
  27. 14 Jun, 2016 1 commit