1. 08 Jun, 2017 1 commit
  2. 28 Feb, 2017 1 commit
  3. 03 Feb, 2017 1 commit
    • Nikolai Kosjar's avatar
      CppEditor: Rework showing/switching parse configurations · 38ba61ec
      Nikolai Kosjar authored
      * Move the combox box for switching the parse configurations out of the
        "Additional Preprocessor Directives" dialog ('#'-button) to make it
        better visible/accessible. Also, decouple the extra preprocessor
        directives from the concrete parse context since this is not anymore
        in same dialog.
      * The combo box appears only if multiple parse configurations are
        available for a file.
      * The first time multiple parse configurations are detected, an info bar
        is shown that points the user to the combox box. A "Do Not Show Again"
        button is provided.
      * Upon selecting an entry, the preferred parse configuration is saved as
        part of the session. The setting can be cleared with the context menu
        entry on the combo box.
      Follow-up changes need to ensure that the display name and/or tooltip is
      unambiguous, e.g. for qbs and cmake projects.
      Change-Id: I9e9773704187291524ad7b605bfdddd83ef5b19d
      Reviewed-by: David Schulz's avatarDavid Schulz <david.schulz@qt.io>
  4. 24 Jan, 2017 1 commit
  5. 16 Jan, 2017 1 commit
  6. 16 Dec, 2016 3 commits
  7. 23 Nov, 2016 1 commit
    • Nikolai Kosjar's avatar
      Clang: Fix initial document parse with modified content · 6cf1f796
      Nikolai Kosjar authored
      Reproduce with:
        1. Create a new class named Foo with the wizard.
        2. Close foo.h
        3. In foo.cpp, add some class member function.
        4. In foo.cpp, trigger the refactoring action "Add public Declaration"
           for the just defined member function. As a result, foo.h will be
           ==> While the declaration was added, the header file is not yet
               reparsed with the new content - this can be verified by setting
               a custom color for "Function".
      In this use case, the refactoring action opens the editor and
      immediately modifies the document (RefactoringFile::apply).
      Fix by sending the document content along for the very first
      RegisterTranslationUnitForEditorMessage if the document was already
      Change-Id: If20615a45b72dd0bef87e1870e403d0b277bc5d6
      Reviewed-by: David Schulz's avatarDavid Schulz <david.schulz@qt.io>
  8. 16 Nov, 2016 1 commit
  9. 21 Oct, 2016 1 commit
  10. 11 Oct, 2016 1 commit
    • Nikolai Kosjar's avatar
      Clang: Show info bar for parse errors in header files · 9d55d848
      Nikolai Kosjar authored
      ...because those errors can lead to a substantial performance/functional
      The actual diagnostics (possibly with children) are shown as details in
      the info bar.
      The info bar can be hidden with the "Do Not Show Again" button.
      Re-enabling the info bar is possible with the new editor tool bar
      Change-Id: I03394ff8e3c84127946b0b791930b28a385f5a46
      Reviewed-by: David Schulz's avatarDavid Schulz <david.schulz@qt.io>
  11. 10 Oct, 2016 1 commit
    • Nikolai Kosjar's avatar
      Clang: Hook up supportive translation unit on first edit · 380d756a
      Nikolai Kosjar authored
      Parsing happens rotationally on the translation units.
      The recently parsed translation unit is used for completion jobs while
      the older version is used for parse jobs.
        A1. A completion job cannot be blocked anymore by currently running
            parse job.
        A2. Faster triggering of parse jobs. A reparse was triggered about
            1650ms after the last keystroke. This is down to 500ms now since we
            do not have a blocking translation unit for the completion anymore.
        D1. Memory consumption is doubled for an edited document.
            This could be addressed by suspending the second translation unit
            after some time of inactivity.
        D2. Setup of the supportive translation unit takes some time.
      Change-Id: I958c883c01f274530f5482c788c15cd38d6f4c3e
      Reviewed-by: David Schulz's avatarDavid Schulz <david.schulz@qt.io>
  12. 25 Jul, 2016 1 commit
  13. 18 Jul, 2016 1 commit
  14. 01 Mar, 2016 2 commits
  15. 16 Feb, 2016 1 commit
  16. 15 Feb, 2016 1 commit
  17. 12 Feb, 2016 2 commits
  18. 19 Jan, 2016 1 commit
  19. 13 Jan, 2016 1 commit
  20. 12 Jan, 2016 2 commits
  21. 16 Dec, 2015 3 commits
  22. 07 Dec, 2015 1 commit
  23. 02 Dec, 2015 1 commit
  24. 01 Dec, 2015 1 commit
  25. 30 Nov, 2015 4 commits
  26. 26 Nov, 2015 1 commit
  27. 25 Nov, 2015 1 commit
  28. 11 Nov, 2015 2 commits
  29. 06 Nov, 2015 1 commit