MirBSD manpage: glEdgeFlag(3), glEdgeFlagv(3)

GLEDGEFLAG(3G)      UNIX Programmer's Manual       GLEDGEFLAG(3G)


     glEdgeFlag, glEdgeFlagv - flag edges as either boundary or


     void glEdgeFlag( GLboolean flag )


     flag  Specifies the current edge flag value, either GL_TRUE
           or GL_FALSE. The initial value is GL_TRUE.


     void glEdgeFlagv( const GLboolean *flag )


     flag Specifies a pointer to an array that contains a single
          boolean element, which replaces the current edge flag


     Each vertex of a polygon, separate triangle, or separate
     quadrilateral specified between a glBegin/glEnd pair is
     marked as the start of either a boundary or nonboundary
     edge. If the current edge flag is true when the vertex is
     specified, the vertex is marked as the start of a boundary
     edge. Otherwise, the vertex is marked as the start of a non-
     boundary edge. glEdgeFlag sets the edge flag bit to GL_TRUE
     if flag is GL_TRUE, and to GL_FALSE otherwise.

     The vertices of connected triangles and connected quadrila-
     terals are always marked as boundary, regardless of the
     value of the edge flag.

     Boundary and nonboundary edge flags on vertices are signifi-
     cant only if GL_POLYGON_MODE is set to GL_POINT or GL_LINE.
     See glPolygonMode.


     The current edge flag can be updated at any time. In partic-
     ular, glEdgeFlag can be called between a call to glBegin and
     the corresponding call to glEnd.


     glGet with argument GL_EDGE_FLAG


     glBegin(3G), glEdgeFlagPointer(3G), glPolygonMode(3G)

MirBSD #10-current     Printed 2021-12-07                       1

Generated on 2021-12-07 11:07:08 by $MirOS: src/scripts/roff2htm,v 1.103 2021/01/23 20:24:35 tg Exp $ — This product includes material provided by mirabilos.

These manual pages and other documentation are copyrighted by their respective writers; their sources are available at the project’s CVSweb, AnonCVS and other mirrors. The rest is Copyright © 2002–2021 MirBSD.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report — diffs preferred.