GLEVALPOINT(3G)
π GLEVALPOINT(3G) β glEvalPoint1, glEvalPoint2 π
okay bestie, welcome to the 3G manual page for glEvalPoint1 and glEvalPoint2 β¨ these two are literally the "just gimme ONE point" girlies of the mesh world. let's get into it π«Ά
β¨ NAME β¨
glEvalPoint1, glEvalPoint2 β generate and evaluate a single point in a mesh
πΈ C SPECIFICATION πΈ
void glEvalPoint1( GLint i )
void glEvalPoint2( GLint i,
GLint j )
π PARAMETERS π
iβ Specifies the integer value for grid domain variablei.jβ Specifies the integer value for grid domain variablej(glEvalPoint2only).
π¦ DESCRIPTION π¦
so here's the vibe: glMapGrid and glEvalMesh are used in tandem to efficiently generate and evaluate a series of evenly spaced map domain values. and glEvalPoint can be used to evaluate a single grid point in the same gridspace that is traversed by glEvalMesh π (yes, the same gridspace, no cap).
Calling glEvalPoint1 is equivalent to calling
glEvalCoord1( iβ
Ξu+u1 );
where
Ξu=(u2βu1)/n
and n, u1, and u2 are the arguments to the most recent glMapGrid1 command. and the one absolute numeric requirement β like, the ONE thing you cannot fumble β is that if i=n, then the value computed from iβ
Ξu+u1 is exactly u2. exactly. not "close enough", not "bestie it's basically the same". EXACTLY. π
In the two-dimensional case, glEvalPoint2, let
Ξu=(u2βu1)/n
Ξv=(v2βv1)/m,
where n, u1, u2, m, v1, and v2 are the arguments to the most recent glMapGrid2 command. Then the glEvalPoint2 command is equivalent to calling
glEvalCoord2( iβ
Ξu+u1, jβ
Ξv+v1 );
The only absolute numeric requirements are that if i=n, then the value computed from iβ
Ξu+u1 is exactly u2, and if j=m, then the value computed from iβ
Ξv+v1 is exactly v2. β¨ two requirements, both absolute, both exact. the math does not do vibes-based rounding, she does precision. π§
β ASSOCIATED GETS β
glGetwith argumentGL_MAP1_GRID_DOMAINglGetwith argumentGL_MAP2_GRID_DOMAINglGetwith argumentGL_MAP1_GRID_SEGMENTSglGetwith argumentGL_MAP2_GRID_SEGMENTS
π SEE ALSO π
glEvalCoord(3G), glEvalMesh(3G), glMap1(3G), glMap2(3G), glMapGrid(3G)
and that's the whole page, bestie!! π₯³ this one's from the GLEVALPOINT(3G) manual page, and the footer just says GLEVALPOINT(3G) again with no extra version or date info to spill β so consider this your cute lil sign-off: go forth and evaluate exactly one point at a time, no more no less ππΈπ
π¦ where this page comes from
- opensuse-leap 16.0: Mesa-libGL-devel 24.1.7-160000.3.1 Β· MIT
- opensuse-leap 16.0: Mesa-libGL-devel 24.3.3-160000.3.1 Β· MIT
- opensuse-leap 16.0: Mesa-libGL-devel 24.3.3-160000.3.1 Β· MIT
- opensuse-leap 16.0: Mesa-libGL-devel 24.3.3-160000.3.1 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms