1. 16 Aug, 2015 3 commits
  2. 15 Aug, 2015 10 commits
  3. 14 Aug, 2015 8 commits
  4. 13 Aug, 2015 1 commit
  5. 11 Aug, 2015 3 commits
  6. 10 Aug, 2015 6 commits
  7. 06 Aug, 2015 1 commit
  8. 05 Aug, 2015 1 commit
  9. 04 Aug, 2015 1 commit
  10. 30 Jul, 2015 4 commits
  11. 28 Jul, 2015 1 commit
    • Sebastian Dröge's avatar
      textoverlay: Query downstream caps for checking if caps features are... · 5830db70
      Sebastian Dröge authored
      textoverlay: Query downstream caps for checking if caps features are supported, not just accept-caps
      accept-caps is not recursive and might stop at the next downstream element,
      while caps queries are generally recursive. The next element might accept any
      capsfeatures we want, but that doesn't mean that further downstream it will
      also work.
      Additionally for the future:
      We should probably check if downstream *prefers* the
      overlay meta, and only enforce usage of it if we can't handle
      the format ourselves and thus would have to drop the overlays.
      Otherwise we should prefer what downstream wants here.
  12. 24 Jul, 2015 1 commit
    • Nicolas Dufresne's avatar
      basetextoverlay: Use the extents rectangle for positioning · d4759f05
      Nicolas Dufresne authored
      the extents rectangle is what you need to know to properly position
      a buffer that has been rendered in a surface of the ink rectangle
      size. This patch make the placement on par with the placement we had
      before without having to over allocate.
      This patch also enable placement for vertical rendering. Note that
      the halginement, valighment and line-alignment default are set to
      the previous default when this property is set. This is for backward
      compatibility, you can change the value after setting vertical render.