[mutter/gbsneto/software-picking: 67/67] framebuffer: Fix clip tracking in the unclipped case



commit f72c2ecf96798a085259eb32dac530f06aeb3f63
Author: Jasper St. Pierre <jstpierre mecheye net>
Date:   Sun Nov 17 22:34:49 2013 -0500

    framebuffer: Fix clip tracking in the unclipped case
    
    Leaving the clip bounds untouched means that it will retain the stale value
    of whatever it was when we last had a clip; reset it so that it contains the
    full framebuffer contents instead.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=712562

 cogl/cogl/cogl-framebuffer.c | 17 +++++------------
 1 file changed, 5 insertions(+), 12 deletions(-)
---
diff --git a/cogl/cogl/cogl-framebuffer.c b/cogl/cogl/cogl-framebuffer.c
index 6bfbc5384..40904df14 100644
--- a/cogl/cogl/cogl-framebuffer.c
+++ b/cogl/cogl/cogl-framebuffer.c
@@ -443,18 +443,11 @@ cleared:
 
       /* NB: A clear may be scissored so we need to track the extents
        * that the clear is applicable too... */
-      if (clip_stack)
-        {
-          _cogl_clip_stack_get_bounds (clip_stack,
-                                       &framebuffer->clear_clip_x0,
-                                       &framebuffer->clear_clip_y0,
-                                       &framebuffer->clear_clip_x1,
-                                       &framebuffer->clear_clip_y1);
-        }
-      else
-        {
-          /* FIXME: set degenerate clip */
-        }
+      _cogl_clip_stack_get_bounds (clip_stack,
+                                   &framebuffer->clear_clip_x0,
+                                   &framebuffer->clear_clip_y0,
+                                   &framebuffer->clear_clip_x1,
+                                   &framebuffer->clear_clip_y1);
     }
 }
 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]