1. 27 Jul, 2018 1 commit
  2. 25 Apr, 2018 1 commit
  3. 16 May, 2017 1 commit
  4. 20 Aug, 2016 1 commit
  5. 29 Apr, 2016 1 commit
  6. 13 Apr, 2016 1 commit
  7. 24 Mar, 2016 1 commit
  8. 02 Oct, 2015 1 commit
  9. 06 Jul, 2015 1 commit
  10. 23 Feb, 2015 1 commit
  11. 22 Sep, 2014 1 commit
  12. 16 Sep, 2014 4 commits
    • Antonio Ospite's avatar
      ximagesrc: Remove unused screen-num property · 80fa912b
      Antonio Ospite authored
      The screen number can be still specified as part of the display-name
      property (e.g. for screen 1 of display 0 use display-name=":0.1").
      
      https://bugzilla.gnome.org/show_bug.cgi?id=736122
      80fa912b
    • Antonio Ospite's avatar
      ximagesrc: Draw the cursor only when it is active in the capturing region · 7554bd39
      Antonio Ospite authored
      Use XQueryPointer to check that the pointer is actually active inside
      the capturing region.
      
      This prevents drawing the cursor when the pointer is partially outside
      of the captured region but not active inside the region; in particular
      this avoids drawing the "window resize" cursor shapes to the captured
      image when the mouse pointer crosses a window border.
      
      NOTE that this is not only an optimization, this also happen to fix
      a serious problem in multi-screen setups.
      
      Because XFixes gives no information of what screen the pointer is on,
      ximagesrc was always drawing the cursor on the captured screen even if
      the mouse pointer was on another screen.
      
      For example, when capturing from screen 1 (i.e. display-name=":0.1") the
      cursor was drawn in the captured image even when the mouse pointer was
      actually on screen 0, which is wrong and visually confusing.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=690646
      7554bd39
    • Antonio Ospite's avatar
      ximagesrc: Fix drawing the cursor when it is outside the capturing region · 3705f08b
      Antonio Ospite authored
      When the cursor is partially or totally out of the capturing region on
      the top side or on the left side, it gets drawn fully inside of the
      region with its coordinates rounded up to the left or to the top border.
      
      This is immediately noticeable when using the xid property to capture
      a specific window.
      
      To fix the issue, allow negative cx and cx coordinates when checking the
      boundaries before drawing the cursor.
      
      NOTE that the boundaries checking calculations still allows the cursor
      to be drawn when it is only partially outside of the capturing region,
      but this makes sense and gives a more pleasing visual behaviour.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=690646
      3705f08b
    • Antonio Ospite's avatar
      ximagesrc: Fix the destination coordinates of the cursor · cb70a7f6
      Antonio Ospite authored
      XFixes provides the cursor coordinates relative to the root window, this
      is not taken into account when using the xid property to capture
      a specific window, the result is that the cursor gets drawn at the wrong
      position.
      
      In order to fix this consider the window location when calculating the
      cursor position in the destination image.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=690646
      cb70a7f6
  13. 31 Jul, 2014 2 commits
  14. 21 May, 2014 1 commit
  15. 27 Mar, 2014 2 commits
  16. 18 Nov, 2013 1 commit
  17. 20 Jun, 2013 1 commit
    • Tim-Philipp Müller's avatar
      ximagesrc: clear dts on buffer acquired from pool · c03efd38
      Tim-Philipp Müller authored
      When setting timestamps on outgoing buffers, clear the
      dts explicitly, otherwise it may end up being set to a
      bogus value from last time it was used. Avoids every
      second or so buffer's dts being set to 0. Not that it
      should matter for raw video.
      c03efd38
  18. 15 Apr, 2013 1 commit
  19. 24 Jan, 2013 1 commit
  20. 04 Nov, 2012 1 commit
  21. 03 Oct, 2012 1 commit
  22. 27 Aug, 2012 1 commit
  23. 09 Apr, 2012 1 commit
  24. 05 Apr, 2012 1 commit
  25. 04 Apr, 2012 1 commit
  26. 30 Mar, 2012 1 commit
  27. 27 Mar, 2012 1 commit
  28. 11 Mar, 2012 1 commit
  29. 06 Mar, 2012 1 commit
  30. 05 Mar, 2012 1 commit
  31. 29 Feb, 2012 1 commit
  32. 28 Feb, 2012 1 commit
  33. 24 Feb, 2012 1 commit
  34. 22 Feb, 2012 1 commit
  35. 08 Feb, 2012 1 commit