Lines Matching refs:rectangles
60 rectangles" specified in window-space coordinates that restrict
65 window rectangles are ignored so these window rectangles apply to
69 GL_MAX_WINDOW_RECTANGLES_EXT) number of window rectangles can be
70 operational at once. When one or more window rectangles are active,
72 any of the operational window rectangles (GL_INCLUSIVE_EXT mode) or
74 rectangles (GL_EXCLUSIVE_EXT mode).
76 These window rectangles operate orthogonally to the existing scissor
118 * the window rectangles test (see section 17.3.X);
124 The pixel ownership, window rectangles test, and scissor tests are
137 "The window rectangles test determines if window-space fragment
139 rectangles. The window rectangles are set with
144 generates INVALID_ENUM), /n/ is a count of active window rectangles (and
170 When the window rectangles mode is INCLUSIVE_EXT mode and the
172 rectangles test if the fragment's window-space position is within
173 at least one of the current /n/ active window rectangles; otherwise
174 the window rectangles test fails and the fragment is discarded.
176 When the window rectangles mode is EXCLUSIVE_EXT mode and the bound
177 framebuffer object is non-zero, a fragment fails the window rectangles
179 within at least one of the current /n/ active window rectangles;
180 otherwise the window rectangles test passes and the fragment passes
181 the window rectangles test.
183 When the bound framebuffer object is zero, the window rectangles
186 The state required for the window rectangles test is a bit
192 rectangles. This initial state is EXCLUSIVE_EXT for the bit, all
193 zero for each integer in the array of window rectangles, and zero
202 rectangles test (17.3.X), the scissor test, sRGB conversion (see
219 (section 17.3.1), window rectangles test (section 17.3.X), or scissor
235 ownership test, the window rectangles test, the scissor test, and
246 the pixel ownership test (see section 13.8.1), window rectangles
266 * the window rectangles test (see section 13.8.X);
275 "The window rectangles test determines if window-space fragment
277 rectangles. The window rectangles are set with
282 generates INVALID_ENUM), /n/ is a count of active window rectangles (and
308 When the window rectangles mode is INCLUSIVE_EXT mode and the
310 rectangles test if the fragment's window-space position is within
311 at least one of the current /n/ active window rectangles; otherwise
312 the window rectangles test fails and the fragment is discarded.
314 When the window rectangles mode is EXCLUSIVE_EXT mode and the bound
315 framebuffer object is non-zero, a fragment fails the window rectangles
317 within at least one of the current /n/ active window rectangles;
318 otherwise the window rectangles test passes and the fragment passes
319 the window rectangles test.
321 When the bound framebuffer object is zero, the window rectangles
324 The state required for the window rectangles test is a bit
330 rectangles. This initial state is EXCLUSIVE_EXT for the bit, all
331 zero for each integer in the array of window rectangles, and zero
343 rectangles test (13.8.X), the scissor test, sRGB conversion (see
362 ownership test, the window rectangles test, the scissor test, and
422 …NUM_WINDOW_RECTANGLE_EXT Z+ GetIntegerv 0 Active window rectangles 17.3.X…
434 window rectangles
441 a new per-fragment test, called the window rectangles test,
443 testing those coordinates against a set of rectangles.
451 as the window rectangles test does.
459 coordinates. Multiple such rectangles are supported hence
460 "rectangles" in the name.
462 Intuitively, we can think of the rectangles carving out by
469 RESOLVED: No, configuring zero exclusive window rectangles is
470 the same as disabling window rectangles. Example:
472 // disable window rectangles
475 3) Should all the window rectangles be specified in a single call
480 The expectation is that the configuration of window rectangles
484 rectangle box. This means all the window rectangles must be
488 window rectangles are configured?
490 RESOLVED: Applications should assume window rectangles
492 no cost to enable the window rectangles, even including the
493 implementation-dependent limit number of window rectangles.
495 5) How does this extension's window rectangles interact with OpenGL's
498 RESOLVED: The scissor test and window rectangles are orthogonal.
501 scissor test and window rectangles when the fragment's window space
502 position is within any one of the window rectangles and also
506 scissor test and window rectangles when the fragment's window
508 the window rectangles.
511 implementation-dependent maximum number of window rectangles?
517 clipping region by merging or overlapping window rectangles.
524 rectangles in exclusive mode can be used to avoid rendering
530 the stencil buffer. Managing exclusive window rectangles
538 rectangles can restrict rendering to just the rectangles
546 8) Does the window rectangles test affect rasterization of geometric
547 primitive (polygons, lines, points), image rectangles (glBitmap,
552 9) Does the window rectangles test affect clears?
556 10) If you specify a subset (or none) of the window rectangles,
557 what happens to the state of the unspecified window rectangles?
566 RESOLVED: The values of the window rectangles box elements are
584 13) What happens when the window rectangles mode is GL_INCLUSIVE_EXT but
585 zero window rectangles are specified?
594 window rectangles for that matter).
600 RESOLVED: No, the hardware functionality for window rectangles
612 rectangles test so pbuffers, etc. wouldn't support the window
613 rectangles test.
618 supporting the window rectangles test.
627 The current set of window rectangles applies to rasterization
630 17) Does the window rectangles test affect glBlitFramebuffer and
638 18) Does the window rectangles test affect glAccum operations?
641 accumulation buffer attachments and the window rectangles test
646 language to be added to support window rectangles on FBOs.
656 window rectangles test (section 17.3.X) are updated."
665 test, the window rectangles test (section 17.3.X), the scissor test
669 19) Is glInvalidateSubFramebuffer affected by window rectangles test?
671 RESOLVED: No. The window rectangles test applies to
675 20) Should the window rectangles state be subject to
680 Being able to push/pop window rectangles is a natural notion for
682 to window rectangles.
686 rectangles test discards fragments?
691 Ordering" when the window rectangles test is supported.
692 An implementation could implement the window rectangles test
695 fragment was not discarded by the window rectangles test.
700 rectangles test could be implementing naively, just testing every
705 is the window rectangles are "known up front" so they can be
710 window rectangles rather than naively testing every fragment.
721 By overlapping multiple inclusive window rectangles, the shape
732 25) How does the window rectangles test operated in layered
735 RESOLVED: The window rectangles test affects rendering to any
739 26) Does the window rectangles state affect glReadPixels or the
742 RESOLVED: No. The window rectangles test is a fragment operation
744 window rectangles test state. This is matches the behavior of
747 That said, the window rectangles test does affect the
750 pixels that will be discarded by the window rectangles test on
752 rectangles test on a blit or copy operation.
764 While NVIDIA GPUs can support 8 window rectangles, feedback from