1. 17 May, 2010 2 commits
  2. 14 May, 2010 4 commits
  3. 11 May, 2010 1 commit
    • Thorbjørn Lindeijer's avatar
      Fixed completion settings to also apply to the QML code completion · e53b5bc9
      Thorbjørn Lindeijer authored
      
      
      By moving the completion settings into the TextEditor plugin, so that
      both the CppTools and the QmlJSEditor plugins can access the settings.
      
      The user-interface to edit the settings is still in the CppTools plugin,
      since we're in string freeze at the moment. It should be moved to the
      TextEditor plugin later.
      
      For now the QML completion only supports the case-sensitivity and
      partial completion options, since there is no automatic insertion of
      brackets.
      
      Task-number: QTCREATORBUG-1327
      Reviewed-by: default avatarDaniel Molkentin <daniel.molkentin@nokia.com>
      e53b5bc9
  4. 10 May, 2010 3 commits
  5. 06 May, 2010 1 commit
  6. 05 May, 2010 3 commits
  7. 15 Apr, 2010 1 commit
  8. 09 Apr, 2010 1 commit
  9. 08 Apr, 2010 1 commit
  10. 11 Mar, 2010 1 commit
    • Christian Kamm's avatar
      Make sure the BackwardScanner has tokenized before asking for a string. · 5a7858f5
      Christian Kamm authored
      The problem was that for
      
      Foo::Foo
      (|)
      
      when the user triggers completion at |, startOfLine() returns a token
      that's not on the current line and not yet tokenized by that instance
      of the BackwardScanner.
      
      As a fix I explicitly ask the instance to tokenize up to the given
      index.
      
      Task-number: QTCREATORBUG-673
      Reviewed-by: Roberto Raggi
      5a7858f5
  11. 05 Mar, 2010 2 commits
  12. 22 Feb, 2010 1 commit
  13. 15 Feb, 2010 2 commits
  14. 01 Feb, 2010 1 commit
  15. 26 Jan, 2010 1 commit
  16. 20 Jan, 2010 1 commit
  17. 14 Jan, 2010 1 commit
  18. 12 Jan, 2010 1 commit
  19. 11 Jan, 2010 1 commit
  20. 07 Jan, 2010 1 commit
    • Thorbjørn Lindeijer's avatar
      Use the completion case sensitivity settings also for relevance · aeaaa392
      Thorbjørn Lindeijer authored
      Avoids some annoyance for people using case-sensitive completion, when
      unrelated completions items would get higher relevance because they
      start with the typed string when matched case-insensitively.
      
      In case-insensitive mode, a case-sensitive prefix match now does get a
      higher relevance than a case-insensitive match.
      
      Reviewed-by: con
      aeaaa392
  21. 11 Dec, 2009 1 commit
    • Thorbjørn Lindeijer's avatar
      Be smarter about CamelCase when doing case-insensitive completion · 46e61276
      Thorbjørn Lindeijer authored
      Even when an upper case character can also match a lower case one, it
      should only be treated as a CamelCase match when the matched character
      is also upper case. This avoids some false positives.
      
      Also, the part that allows a word in a CamelCase identifier to be
      truncated should never be matched case-insensitively.
      46e61276
  22. 10 Dec, 2009 1 commit
  23. 09 Dec, 2009 1 commit
  24. 08 Dec, 2009 1 commit
  25. 07 Dec, 2009 1 commit
  26. 02 Dec, 2009 1 commit
  27. 01 Dec, 2009 1 commit
  28. 20 Nov, 2009 1 commit
  29. 19 Nov, 2009 1 commit
  30. 17 Nov, 2009 1 commit