1. 16 Nov, 2015 2 commits
  2. 12 Nov, 2015 3 commits
  3. 05 Nov, 2015 2 commits
  4. 03 Nov, 2015 1 commit
  5. 02 Nov, 2015 1 commit
  6. 30 Oct, 2015 1 commit
    • Ulf Hermann's avatar
      QmlProfiler: Don't needlessly delete debug connections · ccb6d613
      Ulf Hermann authored
      
      
      If we're already trying to connect when the "Waiting for ..." message
      arrives we don't want to start from scratch, but rather reuse the
      existing connection.
      
      Otherwise the handshake may be interrupted in an arbitrary state,
      either leaving the remote QML engine waiting for the local QML profiler
      to send the recording status, or prompting the local profiler client to
      stop recording as the connection "broke".
      
      The local QML profiler will only send the recording status if new QML
      engines show up, which doesn't happen on the second successful
      connection. That may be a different bug.
      
      Change-Id: Ia17fcf9d0a28edf700274bcd88c2b7030220c290
      Reviewed-by: default avatarRobert Loehning <robert.loehning@theqtcompany.com>
      Reviewed-by: default avatarJoerg Bornemann <joerg.bornemann@theqtcompany.com>
      ccb6d613
  7. 23 Oct, 2015 1 commit
  8. 20 Oct, 2015 2 commits
  9. 02 Oct, 2015 1 commit
  10. 29 Sep, 2015 1 commit
  11. 25 Sep, 2015 1 commit
  12. 17 Sep, 2015 1 commit
  13. 15 Sep, 2015 2 commits
  14. 11 Sep, 2015 8 commits
  15. 10 Sep, 2015 1 commit
  16. 09 Sep, 2015 1 commit
  17. 02 Sep, 2015 2 commits
  18. 01 Sep, 2015 3 commits
  19. 31 Aug, 2015 1 commit
  20. 24 Aug, 2015 1 commit
  21. 17 Aug, 2015 1 commit
    • Ulf Hermann's avatar
      Tell the QML debug server exactly what services we expect · 5f90990c
      Ulf Hermann authored
      
      
      The services need to be loaded before the first QML engine is created.
      The first QML engine may be created before a client connects. When the
      JavaScript debug service is loaded the engine is put into interpreter
      mode as we don't support debugging in JIT mode. Profiling, however
      should be done in JIT mode, whenever possible.
      
      Thus, in order to avoid the loading of unnecessary plugins and to get
      better results from the QML profiler we tell the debug server which
      services we expect, even before the client connects. Qt 5.6 will support
      additional command line arguments to specify the services and this
      change uses them.
      
      Change-Id: I6dcee016c39995e9adada6eaf0e39d8299c9b7e7
      Reviewed-by: default avatarChristian Kandeler <christian.kandeler@theqtcompany.com>
      Reviewed-by: default avatarhjk <hjk@theqtcompany.com>
      5f90990c
  22. 28 Jul, 2015 1 commit
  23. 08 Jul, 2015 2 commits