1. 10 May, 2017 1 commit
  2. 25 Apr, 2017 1 commit
  3. 21 Apr, 2017 1 commit
  4. 19 Apr, 2017 1 commit
  5. 17 Mar, 2017 1 commit
  6. 14 Feb, 2017 1 commit
  7. 30 Jan, 2017 1 commit
  8. 23 Jan, 2017 1 commit
  9. 20 Dec, 2016 1 commit
  10. 01 Dec, 2016 2 commits
  11. 11 Nov, 2016 1 commit
  12. 27 Oct, 2016 1 commit
  13. 12 Oct, 2016 1 commit
  14. 10 Oct, 2016 1 commit
  15. 29 Aug, 2016 1 commit
  16. 08 Aug, 2016 1 commit
  17. 02 Aug, 2016 1 commit
  18. 19 Jul, 2016 1 commit
  19. 06 Jul, 2016 2 commits
  20. 20 Jun, 2016 1 commit
  21. 09 Jun, 2016 1 commit
  22. 30 May, 2016 1 commit
  23. 20 May, 2016 1 commit
  24. 18 May, 2016 1 commit
  25. 13 May, 2016 1 commit
    • Christian Kandeler's avatar
      Set the right version number on our binaries. · 87e8f03c
      Christian Kandeler authored
      While we have not encountered issues so far with using the default
      values, it seems more correct to set the version so that e.g. on Unix
      a library's soname contains the actual Qt Creator major version etc.
      For good measure, also set the compatibility version on OS X.
      
      Change-Id: I956c473e0b440fc87ffe1aaf99af626da733b5fb
      Reviewed-by: Eike Ziller's avatarEike Ziller <eike.ziller@qt.io>
      87e8f03c
  26. 11 May, 2016 1 commit
  27. 26 Apr, 2016 1 commit
  28. 22 Apr, 2016 1 commit
  29. 21 Apr, 2016 1 commit
  30. 30 Mar, 2016 1 commit
  31. 17 Mar, 2016 1 commit
    • hjk's avatar
      Relax use of QT_NO_CAST_FROM_ASCII to QT_RESTRICTED_CAST_FROM_ASCII · 82a523f6
      hjk authored
      This is an opt-in trade-off between type safety and user
      code convenience.
      
      QT_NO_CAST_FROM_ASCII is highly beneficial to avoid unintended
      conversions from 8 bit data with potentially "unsuitable"
      encodings to QString. However, it has the undesirable side-effect
      to require user code to wrap character and string literals
      in QLatin1Char(...) and QLatin1String(...) or use similar
      construction, cluttering the code significantly.
      
      QT_RESTRICTED_CAST_FROM_ASCII macro works almost as
      QT_NO_CAST_FROM_ASCII, except that it enables the QChar(char)
      constructor and adds an additional QString(const char (&ch)[N])
      constructor that matches C++ string literals, but no arbitrary
      character pointers.
      
      This avoids a significant share of the need to clutter the
      user code by only a slight relaxation of the type-safety.
      
      Change-Id: I64e0430bb1352edcedf7e19ee25c16408727084c
      Reviewed-by: Orgad Shaneh's avatarOrgad Shaneh <orgads@gmail.com>
      Reviewed-by: default avatarEike Ziller <eike.ziller@theqtcompany.com>
      82a523f6
  32. 08 Mar, 2016 1 commit
  33. 17 Dec, 2015 1 commit
  34. 15 Dec, 2015 1 commit
  35. 04 Dec, 2015 1 commit
  36. 30 Oct, 2015 1 commit
  37. 30 Sep, 2015 1 commit
  38. 22 Sep, 2015 1 commit