1. 10 Oct, 2013 1 commit
  2. 22 Aug, 2013 1 commit
  3. 20 Aug, 2013 1 commit
  4. 25 Jul, 2013 1 commit
  5. 17 Jul, 2013 1 commit
  6. 11 Jun, 2013 1 commit
  7. 24 May, 2013 1 commit
  8. 18 Apr, 2013 1 commit
  9. 16 Apr, 2013 1 commit
  10. 10 Apr, 2013 2 commits
  11. 03 Apr, 2013 1 commit
  12. 04 Mar, 2013 1 commit
  13. 26 Feb, 2013 1 commit
    • Erik Verbruggen's avatar
      C++: Fix/tune semantic highlighter result chunk size. · 2d3d53a0
      Erik Verbruggen authored
      The fix: when finished with a FunctionDefinition, only flush when the
      number of usages reaches the chunk size. This should prevent a lot of
      chunks with a low number of usages for files with short methods.
      
      The tuning: for files larger than 10000 lines, use a larger chunk size
      to prevent the UI thread from having to re-layout/re-paint too often.
      
      Change-Id: I419174d306b8380c6fa8402825767e26c73f62ec
      Reviewed-by: default avatarNikolai Kosjar <nikolai.kosjar@digia.com>
      2d3d53a0
  14. 19 Feb, 2013 1 commit
  15. 11 Feb, 2013 1 commit
  16. 30 Jan, 2013 1 commit
  17. 29 Jan, 2013 3 commits
  18. 22 Jan, 2013 1 commit
  19. 08 Jan, 2013 1 commit
    • Orgad Shaneh's avatar
      Remove braces for single lines of conditions · 29a93998
      Orgad Shaneh authored
      #!/usr/bin/env ruby
      
      Dir.glob('**/*.cpp') { |file|
        # skip ast (excluding paste, astpath, and canv'ast'imer)
        next if file =~ /ast[^eip]|keywords\.|qualifiers|preprocessor|names.cpp/i
        s = File.read(file)
        next if s.include?('qlalr')
        orig = s.dup
        s.gsub!(/\n *if [^\n]*{\n[^\n]*\n\s+}(\s+else if [^\n]* {\n[^\n]*\n\s+})*(\s+else {\n[^\n]*\n\s+})?\n/m) { |m|
          res = $&
          if res =~ /^\s*(\/\/|[A-Z_]{3,})/ # C++ comment or macro (Q_UNUSED, SDEBUG), do not touch braces
            res
          else
            res.gsub!('} else', 'else')
            res.gsub!(/\n +} *\n/m, "\n")
            res.gsub(/ *{$/, '')
          end
        }
        s.gsub!(/ *$/, '')
        File.open(file, 'wb').write(s) if s != orig
      }
      
      Change-Id: I3b30ee60df0986f66c02132c65fc38a3fbb6bbdc
      Reviewed-by: default avatarhjk <qthjk@ovi.com>
      29a93998
  20. 26 Nov, 2012 3 commits
  21. 22 Nov, 2012 1 commit
  22. 05 Oct, 2012 1 commit
  23. 19 Sep, 2012 2 commits
  24. 29 Aug, 2012 1 commit
  25. 17 Aug, 2012 1 commit
  26. 30 Jul, 2012 1 commit
  27. 19 Jul, 2012 1 commit
  28. 17 Jul, 2012 2 commits
    • Leandro Melo's avatar
      C++: Change back highlighting of types · 441c652c
      Leandro Melo authored
      The type highlighting change part of the recent patch
      4a2a17af didn't seem to
      please much from a visual point of view. It's a better
      idea to keep the type highlighting as it was for now
      and in the future try again the approach with an explicit
      option and perhaps a more restrictive context.
      
      The other patch is not reverted entirely because it does
      fix a couple of bugs.
      
      Change-Id: I806afa3d8c1c4b241080b8704255d737f61ee12c
      Reviewed-by: default avatarRoberto Raggi <roberto.raggi@nokia.com>
      441c652c
    • Leandro Melo's avatar
      C++: Changes in semantic highlighting · 4a2a17af
      Leandro Melo authored
      - Fix issues with virtual/non-virtual destructors. They were not
        being correctly identified in some cases - in particular on certain
        uses in derived classes.
      
      - Since now we do have a highlighting item for regular functions,
        constructors and destructors are now highlighted as such. This is
        more semantically correct and actually makes navigation and readiblity
        more distinguishable, since it cleary differentiates the type itself
        from its uses in expressions and declarators. (This seems to be what
        other IDEs like Eclipse, Visual Studio, KDevelop are doing.)
      
        NOTE: There's a switch to disable this item in the case it doesn't
        get good acceptance. Actually, the switch can be made a user
        setting...?
      
      - Change the default color scheme so regular and virtual functions
        have the same color (virtuals continue to be italic). This makes
        sense given the above mentioned changes in constructors/destructors
        highlighting behavior. (In other schemes virtual funcions don't have
        different color, so this shouldn't be necessary in those.)
      
      - Small renaming: "members" are now "fields" - consistent, since
        they apply for data and it's the term used in the UI.
      
      Change-Id: Ib1aa9c0bbf28a31d09f5696460b0095fbe29de80
      Reviewed-by: default avatarRoberto Raggi <roberto.raggi@nokia.com>
      4a2a17af
  29. 05 Jun, 2012 1 commit
    • Francois Ferrand's avatar
      CppHighlighter: highlight all functions/methods. · 809611f3
      Francois Ferrand authored
      - Highlight all function/methods (not just virtual methods).
      - Highlight as a function even if number of arguments does not match. In
        that case, add a diagnostic message to indicate there are too many/too
        few arguments.
      - Fix highlighting of parameters in function declarations.
        These used to be handled indiferently, and they could be mistaken for
        type or field references.
      - Properly highlight template method calls.
      
      Change-Id: I6e61c9ee47763db95c62314f9cc1c4d398df38b3
      Reviewed-by: default avatarLeandro Melo <leandro.melo@nokia.com>
      809611f3
  30. 13 Apr, 2012 1 commit
  31. 29 Mar, 2012 2 commits
  32. 23 Feb, 2012 1 commit