1. 27 Sep, 2012 2 commits
  2. 19 Jul, 2012 1 commit
  3. 16 Mar, 2012 1 commit
    • Thomas Hartmann's avatar
      QmlDesigner: crash fix · 86487d82
      Thomas Hartmann authored
      
      
      It was a very stupid idea to call QApplication::processEvents(); here
      to avoid hickups.
      
      The processEvents() forces the whole designDocumentController managment to be
      be reentrant which it clearly is not (and should not be).
      The reason is simply that resetView is called from there.
      Adding a "flag" for the processEvents is also not a reasonable option.
      This was just very bad style.
      So I remove it.
      
      Task-number: QTCREATORBUG-7120
      Change-Id: I111cf9421f63b9ce44488f0d274624ff48777cef
      Reviewed-by: default avatarKai Koehne <kai.koehne@nokia.com>
      86487d82
  4. 06 Mar, 2012 1 commit
  5. 15 Feb, 2012 1 commit
  6. 26 Jan, 2012 1 commit
  7. 03 Nov, 2011 1 commit
  8. 14 Oct, 2011 1 commit
  9. 22 Jul, 2011 1 commit
  10. 18 Jul, 2011 1 commit
  11. 15 Jul, 2011 1 commit
  12. 28 Jun, 2011 1 commit
  13. 09 Jun, 2011 1 commit
  14. 20 May, 2011 1 commit
  15. 16 May, 2011 1 commit
  16. 06 May, 2011 2 commits
  17. 18 Apr, 2011 2 commits
  18. 13 Apr, 2011 1 commit
  19. 05 Apr, 2011 1 commit
  20. 31 Mar, 2011 1 commit
    • Thomas Hartmann's avatar
      QmlDesigner.propertyEditor: crash fix for setting expressions · 895442d6
      Thomas Hartmann authored
      The problem was that the transaction was commited outside of the try {}
      catch {} block (RAII)
      
      1. I extended to the try block arround the fxObjectNode.setVariantProperty()
      to avoid similar bugs
      2. I force a commit of the transaction before leaving the try block
      
      result:
      If anything is wrong with the entered expression an exception is thrown
      (like before) but now is is catched and we show a messagebox.
      
      Reviewed-by: Kai Koehne
      Task-number: QTCREATORBUG-4312
      895442d6
  21. 30 Mar, 2011 1 commit
  22. 23 Mar, 2011 1 commit
    • Thomas Hartmann's avatar
      QmlDesigner: fixes state editing in text · 37433e2b
      Thomas Hartmann authored
      In the stateseditor we have to use propertiesRemoved instead of
      propertiesAboutToBeRemoved when reseting the model. Otherwise
      the change we want to react to has not happened, yet.
      Some sanity checking in the property editor.
      
      In the DesignDocumentController we slightly change the order.
      The textMoifider is activated (again) before we set back the old
      state.
      Note: We do check for isValid() since the rewriter might delete the state.
      
      
      Reviewed-by: Kai Koehne
      Task-number: QTCREATORBUG-4199
      37433e2b
  23. 22 Mar, 2011 1 commit
  24. 21 Mar, 2011 1 commit
  25. 18 Mar, 2011 1 commit
  26. 09 Mar, 2011 1 commit
  27. 08 Mar, 2011 2 commits
  28. 04 Mar, 2011 1 commit
  29. 01 Mar, 2011 2 commits
  30. 25 Feb, 2011 1 commit
  31. 03 Feb, 2011 1 commit
  32. 12 Jan, 2011 2 commits
  33. 22 Dec, 2010 1 commit
  34. 17 Dec, 2010 1 commit