Skip to content
Snippets Groups Projects
  1. May 17, 2010
  2. May 14, 2010
  3. May 11, 2010
    • 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. May 10, 2010
  5. May 06, 2010
  6. May 05, 2010
  7. Apr 15, 2010
  8. Apr 09, 2010
  9. Apr 08, 2010
  10. Mar 11, 2010
    • 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. Mar 05, 2010
  12. Feb 22, 2010
  13. Feb 15, 2010
  14. Feb 01, 2010
  15. Jan 26, 2010
  16. Jan 20, 2010
  17. Jan 14, 2010
  18. Jan 12, 2010
  19. Jan 11, 2010
  20. Jan 07, 2010
    • 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. Dec 11, 2009
    • 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. Dec 10, 2009
  23. Dec 09, 2009
  24. Dec 08, 2009
  25. Dec 07, 2009
  26. Dec 02, 2009
  27. Dec 01, 2009
  28. Nov 20, 2009
  29. Nov 19, 2009
  30. Nov 17, 2009
Loading