1. 12 Aug, 2021 - 1 commit
  2. 24 May, 2021 - 1 commit
  3. 02 Dec, 2020 - 1 commit
    • Andreas Buhr's avatar
      Fix links to images in documentation · 2910bb5d
      Andreas Buhr authored
      
      Documentation was using the image transparentBorder.png two times, but
      that image file did not exist. This patch changes to use the files
      Glow-transparentBorder.png and DropShadow-transparentBorder.png, which
      were probably intended.
      
      Task-number: QTBUG-88533
      Change-Id: I321146bf911b80340a501dcaa9d41d09abd715ba
      Reviewed-by: default avatarLaszlo Agocs <laszlo.agocs@qt.io>
      2910bb5d
  4. 25 Nov, 2020 - 1 commit
  5. 11 Nov, 2020 - 1 commit
  6. 20 Oct, 2020 - 3 commits
  7. 15 Sep, 2020 - 1 commit
    • Eskil Abrahamsen Blomfeldt's avatar
      Fix effects for dynamic source item updates · 3a7181de
      Eskil Abrahamsen Blomfeldt authored
      d53af701 aimed to fix graphical
      effects when the image source was cleared programmatically after
      the shader effect had been initialized.
      
      The fix made the assumption that the source size of the proxy
      had been bound to the size of the input, but this turned out
      to be wrong for many of the effects.
      
      Further investigation revealed that the graphical effects were
      never written to support source items with properties that
      change. For instance, if you initialize the source image with
      fill mode == Stretch, it would pick the direct throughput
      mode and this would stick, even if you change the fill mode
      later on, causing rendering errors.
      
      Similarly, if you dynamically add children to a childless
      source item at runtime, the effect would not be applied to
      these items since the proxy render mode is required for that.
      
      d53af701
      
       was only added to
      5.15 because that is where the regression is visible, but
      it turns out that this is a general problem in effects which
      is also visible in Qt 6, both as rendering errors and also
      as unpredictable performance implications, where the order
      of operations can decide which mode of throughput you would
      end up with.
      
      The fix is to redo the polish whenever someone changes any
      of the properties that might affect the choice of code path.
      
      Task-number: QTBUG-84686
      Pick-to: 5.15
      Change-Id: I4af494a7a7fabe496e2d3442084cb823ec177b04
      Reviewed-by: default avatarLaszlo Agocs <laszlo.agocs@qt.io>
      3a7181de
  8. 03 Sep, 2020 - 1 commit
  9. 17 Aug, 2020 - 1 commit
  10. 29 Jul, 2020 - 2 commits
  11. 28 Jul, 2020 - 1 commit
  12. 27 Jul, 2020 - 1 commit
  13. 17 Jul, 2020 - 2 commits
  14. 16 Jul, 2020 - 1 commit
  15. 13 Jul, 2020 - 1 commit
  16. 06 Jul, 2020 - 2 commits
  17. 03 Jul, 2020 - 1 commit
  18. 02 Jul, 2020 - 2 commits
  19. 01 Jul, 2020 - 2 commits
  20. 30 Jun, 2020 - 3 commits
  21. 29 Jun, 2020 - 2 commits
  22. 26 Jun, 2020 - 1 commit
  23. 25 Jun, 2020 - 2 commits
  24. 24 Jun, 2020 - 2 commits
  25. 23 Jun, 2020 - 2 commits
  26. 16 Jun, 2020 - 2 commits