1. 20 May, 2015 1 commit
  2. 30 Apr, 2015 1 commit
  3. 29 Apr, 2015 1 commit
  4. 27 Apr, 2015 1 commit
  5. 02 Mar, 2015 1 commit
    • Christian Kandeler's avatar
      Disable re-run ability for analyzers. · bcfe1ab4
      Christian Kandeler authored
      
      
      Our analyzers were designed with the assumption that only one of them is
      ever running (e.g. there is only one instance of the respective UI
      element for each Analyzer). Run controls, on the other hand, assume that
      an arbitrary number of them can run concurrently. With "re-run" enabled
      for an analyzer run control, these concepts clash. A quick test shows
      that some analyzers actually crash if you try to re-run them, but even
      if this were not the case, it could not work in a sensible way.
      Perhaps it would make sense to change the analyzer design so that they
      too can run concurrently, but not for 3.4, obviously.
      
      Change-Id: Ie8650eeef0261f2b697269900d5b465aad10aaf2
      Reviewed-by: default avatarhjk <hjk@theqtcompany.com>
      Reviewed-by: default avatarDaniel Teske <daniel.teske@theqtcompany.com>
      bcfe1ab4
  6. 16 Jan, 2015 1 commit
  7. 15 Dec, 2014 1 commit
  8. 14 Oct, 2014 1 commit
  9. 09 Oct, 2014 1 commit
  10. 04 Aug, 2014 1 commit
    • Daniel Teske's avatar
      CustomExecutableRunConfiguration: Remove nested event loop · 5751f711
      Daniel Teske authored
      
      
      Nested event loops are dangerous and in this case lead to a crash.
      So change the api of ensureConfigured to not use a nested event loop.
      The CustomExecutableRunConfiguration then has to manage the dialog more
      explicitly. Also this makes the dialog non modal, since it should then
      cope with every situation.
      
      Task-number: QTCREATORBUG-11416
      Change-Id: I2af782915c148f8dff1b0df54fdb64aa83f684d2
      Reviewed-by: default avatarTobias Hunger <tobias.hunger@digia.com>
      5751f711
  11. 01 Jul, 2014 1 commit
    • Christian Kandeler's avatar
      Always pass Core::Id by value. · 93304df0
      Christian Kandeler authored
      
      
      Currently we pass in some places by value, elsewhere by const ref and
      for some weird reason also by const value in a lot of places. The latter
      is particularly annoying, as it is also used in interfaces and therefore
      forces all implementors to do the same, since leaving the "const" off is
      causing compiler warnings with MSVC.
      
      Change-Id: I65b87dc3cce0986b8a55ff6119cb752361027803
      Reviewed-by: default avatarhjk <hjk121@nokiamail.com>
      93304df0
  12. 16 Jun, 2014 1 commit
  13. 30 May, 2014 1 commit
  14. 08 Jan, 2014 1 commit
  15. 10 Oct, 2013 1 commit
  16. 16 Aug, 2013 1 commit
  17. 13 Aug, 2013 1 commit
  18. 12 Aug, 2013 1 commit
  19. 25 Apr, 2013 1 commit
  20. 08 Apr, 2013 1 commit
  21. 05 Apr, 2013 5 commits
  22. 28 Mar, 2013 1 commit
  23. 26 Mar, 2013 1 commit
  24. 29 Jan, 2013 1 commit
  25. 05 Oct, 2012 1 commit
  26. 28 Sep, 2012 1 commit
  27. 25 Sep, 2012 1 commit
  28. 18 Sep, 2012 1 commit
  29. 05 Sep, 2012 1 commit
  30. 03 Sep, 2012 1 commit
  31. 19 Jul, 2012 1 commit
  32. 21 Jun, 2012 1 commit
    • Tobias Hunger's avatar
      Profile introduction · 24314562
      Tobias Hunger authored
      
      
      Introduce Profiles to store sets of values that describe a system/device.
      
      These profiles are held by a target, getting rid of much of the information
      stored in the Build-/Run-/DeployConfigurations, greatly simplifying those.
      
      This is a squash of the wip/profile branch which has been on gerrit for a
      while, rebased to current master.
      
      Change-Id: I25956c8dd4d1962b2134bfaa8a8076ae3909460f
      Reviewed-by: default avatarDaniel Teske <daniel.teske@nokia.com>
      24314562
  33. 19 Jun, 2012 1 commit
  34. 25 Apr, 2012 1 commit
  35. 29 Mar, 2012 1 commit
  36. 28 Mar, 2012 1 commit