1. 14 Dec, 2017 1 commit
  2. 06 Dec, 2017 1 commit
  3. 08 Nov, 2017 1 commit
  4. 06 Nov, 2017 1 commit
  5. 17 Oct, 2017 2 commits
  6. 13 Oct, 2017 1 commit
  7. 04 Oct, 2017 2 commits
  8. 13 Sep, 2017 1 commit
  9. 07 Sep, 2017 2 commits
  10. 05 Sep, 2017 1 commit
  11. 23 Aug, 2017 1 commit
  12. 18 Aug, 2017 1 commit
  13. 15 Aug, 2017 1 commit
  14. 17 Jul, 2017 2 commits
  15. 22 Jun, 2017 1 commit
  16. 19 May, 2017 1 commit
  17. 18 May, 2017 1 commit
  18. 03 May, 2017 1 commit
  19. 02 May, 2017 1 commit
  20. 28 Apr, 2017 1 commit
  21. 20 Apr, 2017 1 commit
  22. 21 Mar, 2017 1 commit
    • Ulf Hermann's avatar
      Qml Debugger: Properly handle JavaScript null · f51d554b
      Ulf Hermann authored
      The QML engine might (in the future) actually send the right message
      to indicate a JavaScript null, that is:
      
      { type: "object", value: null }
      
      This piece of JSON is then transformed into a QVariantMap. The QVariant
      that signifies the null is unfortunately different across various Qt
      versions. We can, however, detect it.
      
      Change-Id: I3db42bb35a936bc02c749ab3a136b1d297aefdfe
      Reviewed-by: default avatarhjk <hjk@qt.io>
      f51d554b
  23. 16 Mar, 2017 1 commit
    • Ulf Hermann's avatar
      Qml Debugger: Show fewer messages in the status bar · 38808621
      Ulf Hermann authored
      The QmlDebugConnection can be quite spammy as it repeatedly tries to
      connect to the application. Show error messages from this process in the
      debugger log and only output a line in the status bar if the connection
      is considered to have permanently failed.
      
      Change-Id: I4a5715d9acdac47f690cb8aa67adb5cccff76e11
      Task-number: QTCREATORBUG-17492
      Reviewed-by: default avatarhjk <hjk@qt.io>
      38808621
  24. 15 Mar, 2017 1 commit
    • Ulf Hermann's avatar
      Qml Debugger: Set detailed options rather than "sanity" · 7236f212
      Ulf Hermann authored
      The v4 debug service doesn't understand "sanity" after all, but wants
      to know the features we support. So state that we don't need redundant
      references and that we understand names when sent as strings.
      
      Change-Id: Ie973dd8002935a113a367d098337983d61663265
      Reviewed-by: default avatarhjk <hjk@qt.io>
      7236f212
  25. 13 Mar, 2017 3 commits
    • Ulf Hermann's avatar
      Qml Debugger: Raise sanity level to 1 · f087f362
      Ulf Hermann authored
      This signals that we understand packages without extra "handles",
      that we can deal with only one level of nesting on replies to lookups
      and expression evaluations, and that we can understand script and
      function names transmitted as plain strings rather than refs.
      
      Change-Id: Iffdd50179b8f9374e2fc8ad3a03cf44fbc627bf1
      Task-number: QTBUG-42435
      Reviewed-by: default avatarhjk <hjk@qt.io>
      f087f362
    • Ulf Hermann's avatar
      QmlDebugger: Limit recursive property lookups · fed805d5
      Ulf Hermann authored
      The QML engine will send the number of children in an object as the
      "value" property together with the ref. We can use that to determine
      if an object has children without actually fetching it.
      
      Also, always save the type of a ref, even if we don't know the value
      yet. This avoids redundant lookups.
      
      Task-number: QTBUG-42435
      Change-Id: Ia423b661187dc054fb5782349d1256711ee11265
      Reviewed-by: default avatarhjk <hjk@qt.io>
      fed805d5
    • Ulf Hermann's avatar
      QmlDebugger: Allow functions and scripts to be specified as strings · cb63af70
      Ulf Hermann authored
      For some of those it doesn't make much sense to assign a ref and the
      refs are not stable anyway.
      
      Change-Id: I7b6855225f883b93930b8d501495ef9dd62be7a2
      Reviewed-by: default avatarhjk <hjk@qt.io>
      cb63af70
  26. 08 Mar, 2017 1 commit
  27. 02 Mar, 2017 1 commit
  28. 21 Feb, 2017 1 commit
  29. 19 Jan, 2017 1 commit
    • Ulf Hermann's avatar
      QmlDebugger: Always show a sensible context for the console · 7a432a68
      Ulf Hermann authored
      If the engine is running and no specific context is selected, then it's
      the global QML context. The same holds if the engine is running, but
      the server doesn't support contextual evaluation. If the engine is
      stopped, then it's a frame in the stack trace. Otherwise we don't have
      a context and clear the label.
      
      Change-Id: I5a322098f3297895e07bcc96ee4a5f351423c206
      Reviewed-by: default avatarhjk <hjk@qt.io>
      7a432a68
  30. 13 Dec, 2016 1 commit
  31. 09 Dec, 2016 1 commit
  32. 29 Nov, 2016 1 commit
  33. 04 Nov, 2016 1 commit
  34. 03 Nov, 2016 1 commit