1. 21 Aug, 2017 1 commit
    • Eike Ziller's avatar
      Fix that plugins were wrongly indirectly enabled when testing · 240aff88
      Eike Ziller authored
      
      
      Since the disabling of all plugins except tested onces was implemented
      as an afterthought, it did not update the indirectly enabled plugins.
      Instead, update the list of enabled/disabled plugins in the
      optionsparser like for the -(no)load options, and trigger the update of
      indirectly enabled plugins afterwards. Also take test dependencies into
      account when indirectly enabling plugins directly.
      
      Change-Id: I59d6c05de69a3073576155f7bd6201f1cd44697c
      Reviewed-by: Orgad Shaneh's avatarOrgad Shaneh <orgads@gmail.com>
      240aff88
  2. 14 Apr, 2017 1 commit
  3. 03 Mar, 2017 1 commit
  4. 08 Feb, 2017 1 commit
  5. 11 Jan, 2017 1 commit
  6. 28 Sep, 2016 1 commit
  7. 16 Sep, 2016 1 commit
  8. 06 Sep, 2016 1 commit
  9. 05 Sep, 2016 1 commit
  10. 22 Aug, 2016 1 commit
  11. 09 Aug, 2016 1 commit
  12. 01 Aug, 2016 1 commit
  13. 28 Jul, 2016 1 commit
  14. 24 Jun, 2016 1 commit
  15. 01 Jun, 2016 1 commit
  16. 30 May, 2016 1 commit
  17. 04 May, 2016 1 commit
    • Eike Ziller's avatar
      OS X: Fix regression for opening projects from Finder · fad08a1e
      Eike Ziller authored
      
      
      The kits are restored in delayedInitialize now, but the file open event
      from Finder was delivered before that. That lead to the projects mode
      being opened with the kit configuration screen, but mostly no kits in
      it, when double-clicking a .pro file while Qt Creator is not running.
      
      Delay the remote open file command until plugin initialization is really
      done.
      
      Change-Id: I1a75f6b1f7bcefb4c53d594de11df0d3a0d2e5d3
      Reviewed-by: Tobias Hunger's avatarTobias Hunger <tobias.hunger@qt.io>
      fad08a1e
  18. 11 Feb, 2016 1 commit
  19. 08 Feb, 2016 1 commit
  20. 19 Jan, 2016 1 commit
  21. 07 Sep, 2015 1 commit
  22. 05 Aug, 2015 1 commit
  23. 17 Jun, 2015 1 commit
    • Jarek Kobus's avatar
      Properly delete plugins dependent on failed plugin · 68426717
      Jarek Kobus authored
      
      
      Init all class member pointers to NULL.
      This fixes possible crash on exit when dependent
      plugin was not loaded (e.g. TextEditor was missing).
      In this case plugin's constructor gets called,
      initialize() method is _not_ called
      and destructor gets called -> crash.
      
      Properly delete dependent plugins on
      a plugin which failed to initialize properly.
      
      Fix labels of deleted plugins inside an error dialog
      after pressing "Error Details" from "Installed Plugins"
      dialog.
      
      Change-Id: Iddc029a0f07dcba2501d734d142fb0e69e9383d3
      Reviewed-by: default avatarEike Ziller <eike.ziller@theqtcompany.com>
      68426717
  24. 02 Apr, 2015 1 commit
  25. 01 Apr, 2015 3 commits
    • Eike Ziller's avatar
      PluginManager: Add "-load all" and "-noload all" command line options · 0a294eeb
      Eike Ziller authored
      
      
      Task-number: QTCREATORBUG-11826
      Change-Id: Ia033c1f8c69bbb2c757a0d8284c56168ad88155c
      Reviewed-by: default avatarDaniel Teske <daniel.teske@theqtcompany.com>
      0a294eeb
    • Eike Ziller's avatar
      PluginManager: Behave more like a package manager · 33a5e7d8
      Eike Ziller authored
      
      
      Instead of implicitly disabling plugins if their dependencies are
      disabled, implicitly enable plugins if some enabled plugin needs it.
      That will avoid issues if people disable plugins (e.g. QmlJSTools et al)
      and we later add one of these as a dependency to another plugin (e.g.
      make QmakeProjectManager depend on QmlJSTools), which resulted in the
      previously enabled plugin being implicitly disabled.
      
      Enabling a plugin in About Plugins now asks for all required
      dependencies to be enabled as well.
      Disabling a plugin in About Plugins now asks for disabling all plugins
      that require it.
      Using the -noload command line option now disables all plugins that
      require it in addition.
      Using the -load command line option now implicitly enables all plugins
      that are required.
      Multiple -noload and -load options are handled in the order given on the
      command line.
      
      Task-number: QTCREATORBUG-9131
      Change-Id: I0956106105060a7898a8992e0629009d5ec3ea4d
      Reviewed-by: default avatarDaniel Teske <daniel.teske@theqtcompany.com>
      33a5e7d8
    • Eike Ziller's avatar
      PluginSpec: Naming and encapsulation improvements · d456fd0b
      Eike Ziller authored
      
      
      Prefer enabled state as a property as opposed to disabled state, and
      make setter correspond to getter. Also move setters into private.
      
      Change-Id: I5d002a12f4e540d5b38cc5865490d056ec75f296
      Reviewed-by: default avatarDaniel Teske <daniel.teske@theqtcompany.com>
      d456fd0b
  26. 24 Mar, 2015 1 commit
  27. 16 Mar, 2015 1 commit
  28. 09 Mar, 2015 1 commit
  29. 06 Feb, 2015 1 commit
    • Orgad Shaneh's avatar
      Misc: Remove unneeded qualifications · 74ed591d
      Orgad Shaneh authored
      
      
      Mostly done using the following ruby script:
      Dir.glob('**/*.cpp').each { |file|
        next if file =~ %r{src/shared/qbs|/qmljs/}
        s = File.read(file)
        s.scan(/^using namespace (.*);$/) {
          ns = $1
          t = s.gsub(/^(.*)\b#{ns}::((?!Const)[A-Z])/) { |m|
            before = $1
            char = $2
            if before =~ /"|\/\/|\\|using|SIGNAL|SLOT|Q_/
              m
            else
              before + char
            end
          }
          if t != s
            puts file
            File.open(file, 'w').write(t)
          end
        }
      }
      
      Change-Id: I919da493d0629b719d328e5e71c96a29d230dfd1
      Reviewed-by: default avatarChristian Kandeler <christian.kandeler@theqtcompany.com>
      Reviewed-by: default avatarhjk <hjk@theqtcompany.com>
      74ed591d
  30. 05 Feb, 2015 1 commit
  31. 04 Feb, 2015 3 commits
    • Orgad Shaneh's avatar
      Fix compilation with Qt 5.3 · eb1bcf57
      Orgad Shaneh authored
      
      
      Change-Id: I09c15c797d2cc95f944413a21a37c5a513eed227
      Reviewed-by: default avatarNikolai Kosjar <nikolai.kosjar@theqtcompany.com>
      eb1bcf57
    • Orgad Shaneh's avatar
      Fix compilation with MSVC2010 · f5225c09
      Orgad Shaneh authored
      
      
      Change-Id: Ieb2ba37c0a31ebf89d5d60451022784043945cc4
      Reviewed-by: default avatarNikolai Kosjar <nikolai.kosjar@theqtcompany.com>
      f5225c09
    • Nikolai Kosjar's avatar
      Plugin Tests: Support additional test objects/classes · 4f7eb4e6
      Nikolai Kosjar authored
      
      
      So far tests running within Qt Creator could be implemented with a
      private slot in the plugin class starting with "test".
      
      Binding the test functions to the plugin object/class is fine for test
      functions without side effects. But as soon as side effects come into
      play we need proper initialization and cleanup as it's provided by
      init(), cleanup(), initTestCase() and cleanupTestCase(). However,
      implementing these functions in the plugin class is not appropriate
      since they would affect (potentially quite diverse) test functions.
      
      This patch enables us to provide 'ordinary' test classes in which we can
      handle initialization and clean up the usual way.
      
      In addition to the current test invocations, e.g.:
      
          # (1) Run all test functions of the plugin
          ./qtcreator -test CppTools
      
          # (2) Run selected test functions of the plugin by stating them
          ./qtcreator -test CppTools,test_completion,test_builtinsymbolsearcher
      
          # (3) Run selected test functions of the plugin by a wild card
          # expression
          ./qtcreator -test "CppTools,*pointerdeclaration*"
      
          # (4) Run a test function of the plugin with certain test data
          ./qtcreator -test CppTools,test_completion:template_1
      
      it's now also possible to state the test class in order to execute all
      test functions of that class:
      
          # Run all test functions of a certain class:
          ./qtcreator -test CppTools,SomeClassWithTests
      
      As long as the test class does not start with "test", there should not
      be any problems.
      
      Further, an invocation like (1) now additionally execute all test
      functions of all test classes. For invocations of type (2), (3) and (4)
      all test functions of all test classes are considered, too.
      
      Change-Id: Ief08a6e9e451c599fd0109b8b8e57f92e3ee19f2
      Reviewed-by: default avatarEike Ziller <eike.ziller@theqtcompany.com>
      Reviewed-by: default avatarErik Verbruggen <erik.verbruggen@theqtcompany.com>
      4f7eb4e6
  32. 16 Jan, 2015 2 commits
  33. 15 Jan, 2015 3 commits