Skip to main content

Rendering Pipeline

GfxBase, GfxCore, D3D/OpenGL backends, GfxRender scene graph, and shaders.

Subsystem Metrics​

  • Total Documented Functions: 6265
  • Functions Exercised in Tests: 441
  • Platform-Divergent Implementations: 185
  • Component Source Files: 442

Source Files​

View all 442 source files in this subsystem
Source FilePath
Draw.cppRendering/AppDraw/Draw.cpp
DrawAdorn.cppRendering/AppDraw/DrawAdorn.cpp
HitTest.cppRendering/AppDraw/HitTest.cpp
Draw.hRendering/AppDraw/include/appdraw/Draw.h
DrawAdorn.hRendering/AppDraw/include/appdraw/DrawAdorn.h
Adorn.cppRendering/GfxBase/Adorn.cpp
AdornBillboarder.cppRendering/GfxBase/AdornBillboarder.cpp
AdornBillboarder2D.cppRendering/GfxBase/AdornBillboarder2D.cpp
AdornSurface.cppRendering/GfxBase/AdornSurface.cpp
FileMeshData.cppRendering/GfxBase/FileMeshData.cpp
FrameRateManager.cppRendering/GfxBase/FrameRateManager.cpp
GfxPart.cppRendering/GfxBase/GfxPart.cpp
IAdornableCollector.cppRendering/GfxBase/IAdornableCollector.cpp
PartIdentifier.cppRendering/GfxBase/PartIdentifier.cpp
RenderSettings.cppRendering/GfxBase/RenderSettings.cpp
ViewBase.cppRendering/GfxBase/ViewBase.cpp
ViewportBillboarder.cppRendering/GfxBase/ViewportBillboarder.cpp
Adorn.hRendering/GfxBase/include/GfxBase/Adorn.h
AdornBillboarder.hRendering/GfxBase/include/GfxBase/AdornBillboarder.h
AdornBillboarder2D.hRendering/GfxBase/include/GfxBase/AdornBillboarder2D.h
AdornSurface.hRendering/GfxBase/include/GfxBase/AdornSurface.h
AsyncResult.hRendering/GfxBase/include/GfxBase/AsyncResult.h
FrameRateManager.hRendering/GfxBase/include/GfxBase/FrameRateManager.h
GfxPart.hRendering/GfxBase/include/GfxBase/GfxPart.h
IAdornable.hRendering/GfxBase/include/GfxBase/IAdornable.h
IAdornableCollector.hRendering/GfxBase/include/GfxBase/IAdornableCollector.h
Image.hRendering/GfxBase/include/GfxBase/Image.h
RenderCaps.hRendering/GfxBase/include/GfxBase/RenderCaps.h
RenderSettings.hRendering/GfxBase/include/GfxBase/RenderSettings.h
TextureProxyBase.hRendering/GfxBase/include/GfxBase/TextureProxyBase.h
Typesetter.hRendering/GfxBase/include/GfxBase/Typesetter.h
ViewBase.hRendering/GfxBase/include/GfxBase/ViewBase.h
ViewportBillboarder.hRendering/GfxBase/include/GfxBase/ViewportBillboarder.h
DeviceContextD3D11.cppRendering/GfxCore/D3D11/DeviceContextD3D11.cpp
DeviceD3D11.cppRendering/GfxCore/D3D11/DeviceD3D11.cpp
DeviceD3D11.hRendering/GfxCore/D3D11/DeviceD3D11.h
DeviceD3D11Durango.cppRendering/GfxCore/D3D11/DeviceD3D11Durango.cpp
DeviceD3D11Win32.cppRendering/GfxCore/D3D11/DeviceD3D11Win32.cpp
FramebufferD3D11.cppRendering/GfxCore/D3D11/FramebufferD3D11.cpp
FramebufferD3D11.hRendering/GfxCore/D3D11/FramebufferD3D11.h
GeometryD3D11.cppRendering/GfxCore/D3D11/GeometryD3D11.cpp
GeometryD3D11.hRendering/GfxCore/D3D11/GeometryD3D11.h
OculusVRD3D11.cppRendering/GfxCore/D3D11/OculusVRD3D11.cpp
OpenVRD3D11.cppRendering/GfxCore/D3D11/OpenVRD3D11.cpp
ShaderD3D11.cppRendering/GfxCore/D3D11/ShaderD3D11.cpp
ShaderD3D11.hRendering/GfxCore/D3D11/ShaderD3D11.h
TextureD3D11.cppRendering/GfxCore/D3D11/TextureD3D11.cpp
TextureD3D11.hRendering/GfxCore/D3D11/TextureD3D11.h
DeviceContextD3D9.cppRendering/GfxCore/D3D9/DeviceContextD3D9.cpp
DeviceD3D9.cppRendering/GfxCore/D3D9/DeviceD3D9.cpp
DeviceD3D9.hRendering/GfxCore/D3D9/DeviceD3D9.h
FramebufferD3D9.cppRendering/GfxCore/D3D9/FramebufferD3D9.cpp
FramebufferD3D9.hRendering/GfxCore/D3D9/FramebufferD3D9.h
GeometryD3D9.cppRendering/GfxCore/D3D9/GeometryD3D9.cpp
GeometryD3D9.hRendering/GfxCore/D3D9/GeometryD3D9.h
ShaderD3D9.cppRendering/GfxCore/D3D9/ShaderD3D9.cpp
ShaderD3D9.hRendering/GfxCore/D3D9/ShaderD3D9.h
TextureD3D9.cppRendering/GfxCore/D3D9/TextureD3D9.cpp
TextureD3D9.hRendering/GfxCore/D3D9/TextureD3D9.h
Device.cppRendering/GfxCore/Device.cpp
DeviceCreate.cppRendering/GfxCore/DeviceCreate.cpp
CardboardVRGL.cppRendering/GfxCore/GL/CardboardVRGL.cpp
ContextGL.hRendering/GfxCore/GL/ContextGL.h
ContextGLAndroid.cppRendering/GfxCore/GL/ContextGLAndroid.cpp
ContextGLMac.mmRendering/GfxCore/GL/ContextGLMac.mm
ContextGLWin32.cppRendering/GfxCore/GL/ContextGLWin32.cpp
ContextGLiOS.mmRendering/GfxCore/GL/ContextGLiOS.mm
DeviceContextGL.cppRendering/GfxCore/GL/DeviceContextGL.cpp
DeviceGL.cppRendering/GfxCore/GL/DeviceGL.cpp
DeviceGL.hRendering/GfxCore/GL/DeviceGL.h
FramebufferGL.cppRendering/GfxCore/GL/FramebufferGL.cpp
FramebufferGL.hRendering/GfxCore/GL/FramebufferGL.h
GearVRGL.cppRendering/GfxCore/GL/GearVRGL.cpp
GeometryGL.cppRendering/GfxCore/GL/GeometryGL.cpp
GeometryGL.hRendering/GfxCore/GL/GeometryGL.h
ShaderGL.cppRendering/GfxCore/GL/ShaderGL.cpp
ShaderGL.hRendering/GfxCore/GL/ShaderGL.h
TextureGL.cppRendering/GfxCore/GL/TextureGL.cpp
TextureGL.hRendering/GfxCore/GL/TextureGL.h
Geometry.cppRendering/GfxCore/Geometry.cpp
Resource.cppRendering/GfxCore/Resource.cpp
Shader.cppRendering/GfxCore/Shader.cpp
Texture.cppRendering/GfxCore/Texture.cpp
glew.cRendering/GfxCore/glew/glew.c
glew.cppRendering/GfxCore/glew/glew.cpp
Device.hRendering/GfxCore/include/GfxCore/Device.h
Framebuffer.hRendering/GfxCore/include/GfxCore/Framebuffer.h
Geometry.hRendering/GfxCore/include/GfxCore/Geometry.h
Resource.hRendering/GfxCore/include/GfxCore/Resource.h
States.hRendering/GfxCore/include/GfxCore/States.h
Texture.hRendering/GfxCore/include/GfxCore/Texture.h
pix.cppRendering/GfxCore/pix.cpp
AdornRender.cppRendering/GfxRender/AdornRender.cpp
CullableSceneNode.cppRendering/GfxRender/CullableSceneNode.cpp
CullableSceneNode.hRendering/GfxRender/CullableSceneNode.h
CustomEmitter.cppRendering/GfxRender/CustomEmitter.cpp
Emitter.cppRendering/GfxRender/Emitter.cpp
Emitter.hRendering/GfxRender/Emitter.h
EnvMap.cppRendering/GfxRender/EnvMap.cpp
EnvMap.hRendering/GfxRender/EnvMap.h
ExplosionEmitter.cppRendering/GfxRender/ExplosionEmitter.cpp
FastCluster.cppRendering/GfxRender/FastCluster.cpp
FastCluster.hRendering/GfxRender/FastCluster.h
GeometryGenerator.cppRendering/GfxRender/GeometryGenerator.cpp
GeometryGenerator.hRendering/GfxRender/GeometryGenerator.h
GlobalShaderData.cppRendering/GfxRender/GlobalShaderData.cpp
Image.cppRendering/GfxRender/Image.cpp
Image.hRendering/GfxRender/Image.h
LightGrid.cppRendering/GfxRender/LightGrid.cpp
LightGrid.hRendering/GfxRender/LightGrid.h
LightObject.cppRendering/GfxRender/LightObject.cpp
LightObject.hRendering/GfxRender/LightObject.h
Material.cppRendering/GfxRender/Material.cpp
Material.hRendering/GfxRender/Material.h
MaterialGenerator.cppRendering/GfxRender/MaterialGenerator.cpp
MegaCluster.cppRendering/GfxRender/MegaCluster.cpp
MegaCluster.hRendering/GfxRender/MegaCluster.h
ObjectExporter.cppRendering/GfxRender/ObjectExporter.cpp
ObjectExporter.hRendering/GfxRender/ObjectExporter.h
ParticleEmitter.cppRendering/GfxRender/ParticleEmitter.cpp
RenderCamera.cppRendering/GfxRender/RenderCamera.cpp
RenderCamera.hRendering/GfxRender/RenderCamera.h
RenderNode.cppRendering/GfxRender/RenderNode.cpp
RenderNode.hRendering/GfxRender/RenderNode.h
RenderQueue.cppRendering/GfxRender/RenderQueue.cpp
RenderQueue.hRendering/GfxRender/RenderQueue.h
RenderView.cppRendering/GfxRender/RenderView.cpp
RenderView.hRendering/GfxRender/RenderView.h
SSAO.cppRendering/GfxRender/SSAO.cpp
SSAO.hRendering/GfxRender/SSAO.h
SceneManager.cppRendering/GfxRender/SceneManager.cpp
SceneManager.hRendering/GfxRender/SceneManager.h
SceneUpdater.cppRendering/GfxRender/SceneUpdater.cpp
SceneUpdater.hRendering/GfxRender/SceneUpdater.h
ScreenSpaceEffect.cppRendering/GfxRender/ScreenSpaceEffect.cpp
ShaderManager.cppRendering/GfxRender/ShaderManager.cpp
Sky.cppRendering/GfxRender/Sky.cpp
Sky.hRendering/GfxRender/Sky.h
SmoothCluster.cppRendering/GfxRender/SmoothCluster.cpp
SpatialGrid.hRendering/GfxRender/SpatialGrid.h
SpatialHashedScene.cppRendering/GfxRender/SpatialHashedScene.cpp
SpatialHashedScene.hRendering/GfxRender/SpatialHashedScene.h
SuperCluster.cppRendering/GfxRender/SuperCluster.cpp
SuperCluster.hRendering/GfxRender/SuperCluster.h
TextureAtlas.cppRendering/GfxRender/TextureAtlas.cpp
TextureAtlas.hRendering/GfxRender/TextureAtlas.h
TextureCompositor.cppRendering/GfxRender/TextureCompositor.cpp
TextureCompositor.hRendering/GfxRender/TextureCompositor.h
TextureManager.cppRendering/GfxRender/TextureManager.cpp
TextureManager.hRendering/GfxRender/TextureManager.h
TextureRef.cppRendering/GfxRender/TextureRef.cpp
TextureRef.hRendering/GfxRender/TextureRef.h
TypesetterBitmap.cppRendering/GfxRender/TypesetterBitmap.cpp
TypesetterBitmap.hRendering/GfxRender/TypesetterBitmap.h
TypesetterDynamic.cppRendering/GfxRender/TypesetterDynamic.cpp
Util.hRendering/GfxRender/Util.h
VertexStreamer.cppRendering/GfxRender/VertexStreamer.cpp
VisualEngine.cppRendering/GfxRender/VisualEngine.cpp
VisualEngine.hRendering/GfxRender/VisualEngine.h
Water.cppRendering/GfxRender/Water.cpp
ftcalc.hRendering/GfxRender/freetype/include/freetype/internal/ftcalc.h
ftmemory.hRendering/GfxRender/freetype/include/freetype/internal/ftmemory.h
afcjk.cRendering/GfxRender/freetype/src/autofit/afcjk.c
afdummy.cRendering/GfxRender/freetype/src/autofit/afdummy.c
afglobal.cRendering/GfxRender/freetype/src/autofit/afglobal.c
afhints.cRendering/GfxRender/freetype/src/autofit/afhints.c
afindic.cRendering/GfxRender/freetype/src/autofit/afindic.c
aflatin.cRendering/GfxRender/freetype/src/autofit/aflatin.c
aflatin2.cRendering/GfxRender/freetype/src/autofit/aflatin2.c
afloader.cRendering/GfxRender/freetype/src/autofit/afloader.c
afmodule.cRendering/GfxRender/freetype/src/autofit/afmodule.c
afpic.cRendering/GfxRender/freetype/src/autofit/afpic.c
afwarp.cRendering/GfxRender/freetype/src/autofit/afwarp.c
hbshim.cRendering/GfxRender/freetype/src/autofit/hbshim.c
basepic.cRendering/GfxRender/freetype/src/base/basepic.c
ftadvanc.cRendering/GfxRender/freetype/src/base/ftadvanc.c
ftbbox.cRendering/GfxRender/freetype/src/base/ftbbox.c
ftbitmap.cRendering/GfxRender/freetype/src/base/ftbitmap.c
ftcalc.cRendering/GfxRender/freetype/src/base/ftcalc.c
ftdbgmem.cRendering/GfxRender/freetype/src/base/ftdbgmem.c
ftgloadr.cRendering/GfxRender/freetype/src/base/ftgloadr.c
ftglyph.cRendering/GfxRender/freetype/src/base/ftglyph.c
ftlcdfil.cRendering/GfxRender/freetype/src/base/ftlcdfil.c
ftmac.cRendering/GfxRender/freetype/src/base/ftmac.c
ftmm.cRendering/GfxRender/freetype/src/base/ftmm.c
ftobjs.cRendering/GfxRender/freetype/src/base/ftobjs.c
ftoutln.cRendering/GfxRender/freetype/src/base/ftoutln.c
ftpatent.cRendering/GfxRender/freetype/src/base/ftpatent.c
ftpfr.cRendering/GfxRender/freetype/src/base/ftpfr.c
ftrfork.cRendering/GfxRender/freetype/src/base/ftrfork.c
ftstroke.cRendering/GfxRender/freetype/src/base/ftstroke.c
fttrigon.cRendering/GfxRender/freetype/src/base/fttrigon.c
md5.cRendering/GfxRender/freetype/src/base/md5.c
bdfdrivr.cRendering/GfxRender/freetype/src/bdf/bdfdrivr.c
bdflib.cRendering/GfxRender/freetype/src/bdf/bdflib.c
ftbzip2.cRendering/GfxRender/freetype/src/bzip2/ftbzip2.c
ftccache.cRendering/GfxRender/freetype/src/cache/ftccache.c
ftcmanag.cRendering/GfxRender/freetype/src/cache/ftcmanag.c
ftcsbits.cRendering/GfxRender/freetype/src/cache/ftcsbits.c
cf2arrst.cRendering/GfxRender/freetype/src/cff/cf2arrst.c
cf2font.cRendering/GfxRender/freetype/src/cff/cf2font.c
cf2ft.cRendering/GfxRender/freetype/src/cff/cf2ft.c
cf2hints.cRendering/GfxRender/freetype/src/cff/cf2hints.c
cf2intrp.cRendering/GfxRender/freetype/src/cff/cf2intrp.c
cf2read.cRendering/GfxRender/freetype/src/cff/cf2read.c
cffdrivr.cRendering/GfxRender/freetype/src/cff/cffdrivr.c
cffgload.cRendering/GfxRender/freetype/src/cff/cffgload.c
cffload.cRendering/GfxRender/freetype/src/cff/cffload.c
cffobjs.cRendering/GfxRender/freetype/src/cff/cffobjs.c
cffparse.cRendering/GfxRender/freetype/src/cff/cffparse.c
cffpic.cRendering/GfxRender/freetype/src/cff/cffpic.c
cidload.cRendering/GfxRender/freetype/src/cid/cidload.c
cidobjs.cRendering/GfxRender/freetype/src/cid/cidobjs.c
cidriver.cRendering/GfxRender/freetype/src/cid/cidriver.c
gxvbsln.cRendering/GfxRender/freetype/src/gxvalid/gxvbsln.c
gxvcommn.cRendering/GfxRender/freetype/src/gxvalid/gxvcommn.c
gxvfeat.cRendering/GfxRender/freetype/src/gxvalid/gxvfeat.c
gxvfgen.cRendering/GfxRender/freetype/src/gxvalid/gxvfgen.c
gxvjust.cRendering/GfxRender/freetype/src/gxvalid/gxvjust.c
gxvkern.cRendering/GfxRender/freetype/src/gxvalid/gxvkern.c
gxvlcar.cRendering/GfxRender/freetype/src/gxvalid/gxvlcar.c
gxvmod.cRendering/GfxRender/freetype/src/gxvalid/gxvmod.c
gxvmort.cRendering/GfxRender/freetype/src/gxvalid/gxvmort.c
gxvmort0.cRendering/GfxRender/freetype/src/gxvalid/gxvmort0.c
gxvmort1.cRendering/GfxRender/freetype/src/gxvalid/gxvmort1.c
gxvmort2.cRendering/GfxRender/freetype/src/gxvalid/gxvmort2.c
gxvmort4.cRendering/GfxRender/freetype/src/gxvalid/gxvmort4.c
gxvmort5.cRendering/GfxRender/freetype/src/gxvalid/gxvmort5.c
gxvmorx.cRendering/GfxRender/freetype/src/gxvalid/gxvmorx.c
gxvmorx0.cRendering/GfxRender/freetype/src/gxvalid/gxvmorx0.c
gxvmorx1.cRendering/GfxRender/freetype/src/gxvalid/gxvmorx1.c
gxvmorx2.cRendering/GfxRender/freetype/src/gxvalid/gxvmorx2.c
gxvmorx5.cRendering/GfxRender/freetype/src/gxvalid/gxvmorx5.c
gxvopbd.cRendering/GfxRender/freetype/src/gxvalid/gxvopbd.c
gxvprop.cRendering/GfxRender/freetype/src/gxvalid/gxvprop.c
gxvtrak.cRendering/GfxRender/freetype/src/gxvalid/gxvtrak.c
ftgzip.cRendering/GfxRender/freetype/src/gzip/ftgzip.c
zutil.cRendering/GfxRender/freetype/src/gzip/zutil.c
ftlzw.cRendering/GfxRender/freetype/src/lzw/ftlzw.c
ftzopen.cRendering/GfxRender/freetype/src/lzw/ftzopen.c
otvbase.cRendering/GfxRender/freetype/src/otvalid/otvbase.c
otvcommn.cRendering/GfxRender/freetype/src/otvalid/otvcommn.c
otvgdef.cRendering/GfxRender/freetype/src/otvalid/otvgdef.c
otvgpos.cRendering/GfxRender/freetype/src/otvalid/otvgpos.c
otvgsub.cRendering/GfxRender/freetype/src/otvalid/otvgsub.c
otvjstf.cRendering/GfxRender/freetype/src/otvalid/otvjstf.c
otvmath.cRendering/GfxRender/freetype/src/otvalid/otvmath.c
otvmod.cRendering/GfxRender/freetype/src/otvalid/otvmod.c
pcfdrivr.cRendering/GfxRender/freetype/src/pcf/pcfdrivr.c
pcfread.cRendering/GfxRender/freetype/src/pcf/pcfread.c
pfrgload.cRendering/GfxRender/freetype/src/pfr/pfrgload.c
pfrload.cRendering/GfxRender/freetype/src/pfr/pfrload.c
pfrsbit.cRendering/GfxRender/freetype/src/pfr/pfrsbit.c
afmparse.cRendering/GfxRender/freetype/src/psaux/afmparse.c
psobjs.cRendering/GfxRender/freetype/src/psaux/psobjs.c
t1cmap.cRendering/GfxRender/freetype/src/psaux/t1cmap.c
t1decode.cRendering/GfxRender/freetype/src/psaux/t1decode.c
pshalgo.cRendering/GfxRender/freetype/src/pshinter/pshalgo.c
pshglob.cRendering/GfxRender/freetype/src/pshinter/pshglob.c
pshpic.cRendering/GfxRender/freetype/src/pshinter/pshpic.c
pshrec.cRendering/GfxRender/freetype/src/pshinter/pshrec.c
psmodule.cRendering/GfxRender/freetype/src/psnames/psmodule.c
pspic.cRendering/GfxRender/freetype/src/psnames/pspic.c
pstables.hRendering/GfxRender/freetype/src/psnames/pstables.h
ftmisc.hRendering/GfxRender/freetype/src/raster/ftmisc.h
ftraster.cRendering/GfxRender/freetype/src/raster/ftraster.c
ftrend1.cRendering/GfxRender/freetype/src/raster/ftrend1.c
rastpic.cRendering/GfxRender/freetype/src/raster/rastpic.c
pngshim.cRendering/GfxRender/freetype/src/sfnt/pngshim.c
sfdriver.cRendering/GfxRender/freetype/src/sfnt/sfdriver.c
sfntpic.cRendering/GfxRender/freetype/src/sfnt/sfntpic.c
sfobjs.cRendering/GfxRender/freetype/src/sfnt/sfobjs.c
ttbdf.cRendering/GfxRender/freetype/src/sfnt/ttbdf.c
ttcmap.cRendering/GfxRender/freetype/src/sfnt/ttcmap.c
ttload.cRendering/GfxRender/freetype/src/sfnt/ttload.c
ttpost.cRendering/GfxRender/freetype/src/sfnt/ttpost.c
ttsbit.cRendering/GfxRender/freetype/src/sfnt/ttsbit.c
ftgrays.cRendering/GfxRender/freetype/src/smooth/ftgrays.c
ftsmooth.cRendering/GfxRender/freetype/src/smooth/ftsmooth.c
ftspic.cRendering/GfxRender/freetype/src/smooth/ftspic.c
apinames.cRendering/GfxRender/freetype/src/tools/apinames.c
content.pyRendering/GfxRender/freetype/src/tools/docmaker/content.py
docbeauty.pyRendering/GfxRender/freetype/src/tools/docmaker/docbeauty.py
docmaker.pyRendering/GfxRender/freetype/src/tools/docmaker/docmaker.py
formatter.pyRendering/GfxRender/freetype/src/tools/docmaker/formatter.py
sources.pyRendering/GfxRender/freetype/src/tools/docmaker/sources.py
tohtml.pyRendering/GfxRender/freetype/src/tools/docmaker/tohtml.py
utils.pyRendering/GfxRender/freetype/src/tools/docmaker/utils.py
ftrandom.cRendering/GfxRender/freetype/src/tools/ftrandom/ftrandom.c
glnames.pyRendering/GfxRender/freetype/src/tools/glnames.py
test_afm.cRendering/GfxRender/freetype/src/tools/test_afm.c
test_bbox.cRendering/GfxRender/freetype/src/tools/test_bbox.c
test_trig.cRendering/GfxRender/freetype/src/tools/test_trig.c
ttdriver.cRendering/GfxRender/freetype/src/truetype/ttdriver.c
ttgload.cRendering/GfxRender/freetype/src/truetype/ttgload.c
ttgxvar.cRendering/GfxRender/freetype/src/truetype/ttgxvar.c
ttinterp.cRendering/GfxRender/freetype/src/truetype/ttinterp.c
ttobjs.cRendering/GfxRender/freetype/src/truetype/ttobjs.c
ttpic.cRendering/GfxRender/freetype/src/truetype/ttpic.c
ttsubpix.cRendering/GfxRender/freetype/src/truetype/ttsubpix.c
t1afm.cRendering/GfxRender/freetype/src/type1/t1afm.c
t1driver.cRendering/GfxRender/freetype/src/type1/t1driver.c
t1gload.cRendering/GfxRender/freetype/src/type1/t1gload.c
t1load.cRendering/GfxRender/freetype/src/type1/t1load.c
t1objs.cRendering/GfxRender/freetype/src/type1/t1objs.c
t1parse.cRendering/GfxRender/freetype/src/type1/t1parse.c
t42drivr.cRendering/GfxRender/freetype/src/type42/t42drivr.c
t42objs.cRendering/GfxRender/freetype/src/type42/t42objs.c
t42parse.cRendering/GfxRender/freetype/src/type42/t42parse.c
winfnt.cRendering/GfxRender/freetype/src/winfonts/winfnt.c
Frustum.cppRendering/RbxG3D/Frustum.cpp
RbxCamera.cppRendering/RbxG3D/RbxCamera.cpp
RbxRay.cppRendering/RbxG3D/RbxRay.cpp
Frustum.hRendering/RbxG3D/include/RbxG3D/Frustum.h
RbxCamera.hRendering/RbxG3D/include/RbxG3D/RbxCamera.h
RbxRay.hRendering/RbxG3D/include/RbxG3D/RbxRay.h
main.cppRendering/ShaderCompiler/main.cpp
md5.cRendering/ShaderCompiler/md5/md5.c
AABox.cppRendering/g3d/g3dcpp/AABox.cpp
BinaryInput.cppRendering/g3d/g3dcpp/BinaryInput.cpp
BinaryOutput.cppRendering/g3d/g3dcpp/BinaryOutput.cpp
Box.cppRendering/g3d/g3dcpp/Box.cpp
Capsule.cppRendering/g3d/g3dcpp/Capsule.cpp
CollisionDetection.cppRendering/g3d/g3dcpp/CollisionDetection.cpp
Color3.cppRendering/g3d/g3dcpp/Color3.cpp
Color4.cppRendering/g3d/g3dcpp/Color4.cpp
CoordinateFrame.cppRendering/g3d/g3dcpp/CoordinateFrame.cpp
Crypto.cppRendering/g3d/g3dcpp/Crypto.cpp
Cylinder.cppRendering/g3d/g3dcpp/Cylinder.cpp
GCamera.cppRendering/g3d/g3dcpp/GCamera.cpp
GImage.cppRendering/g3d/g3dcpp/GImage.cpp
GImage_bayer.cppRendering/g3d/g3dcpp/GImage_bayer.cpp
GImage_bmp.cppRendering/g3d/g3dcpp/GImage_bmp.cpp
GImage_jpeg.cppRendering/g3d/g3dcpp/GImage_jpeg.cpp
GImage_png.cppRendering/g3d/g3dcpp/GImage_png.cpp
GImage_tga.cppRendering/g3d/g3dcpp/GImage_tga.cpp
GLight.cppRendering/g3d/g3dcpp/GLight.cpp
LightingParameters.cppRendering/g3d/g3dcpp/LightingParameters.cpp
Line.cppRendering/g3d/g3dcpp/Line.cpp
LineSegment.cppRendering/g3d/g3dcpp/LineSegment.cpp
Matrix3.cppRendering/g3d/g3dcpp/Matrix3.cpp
Matrix4.cppRendering/g3d/g3dcpp/Matrix4.cpp
MemoryManager.cppRendering/g3d/g3dcpp/MemoryManager.cpp
PhysicsFrame.cppRendering/g3d/g3dcpp/PhysicsFrame.cpp
Plane.cppRendering/g3d/g3dcpp/Plane.cpp
Quat.cppRendering/g3d/g3dcpp/Quat.cpp
Random.cppRendering/g3d/g3dcpp/Random.cpp
Ray.cppRendering/g3d/g3dcpp/Ray.cpp
Sphere.cppRendering/g3d/g3dcpp/Sphere.cpp
System.cppRendering/g3d/g3dcpp/System.cpp
Triangle.cppRendering/g3d/g3dcpp/Triangle.cpp
UprightFrame.cppRendering/g3d/g3dcpp/UprightFrame.cpp
Vector2.cppRendering/g3d/g3dcpp/Vector2.cpp
Vector2int16.cppRendering/g3d/g3dcpp/Vector2int16.cpp
Vector3.cppRendering/g3d/g3dcpp/Vector3.cpp
Vector3int16.cppRendering/g3d/g3dcpp/Vector3int16.cpp
Vector4.cppRendering/g3d/g3dcpp/Vector4.cpp
fileutils.cppRendering/g3d/g3dcpp/fileutils.cpp
format.cppRendering/g3d/g3dcpp/format.cpp
g3dfnmatch.cppRendering/g3d/g3dcpp/g3dfnmatch.cpp
g3dmath.cppRendering/g3d/g3dcpp/g3dmath.cpp
stringutils.cppRendering/g3d/g3dcpp/stringutils.cpp
uint128.cppRendering/g3d/g3dcpp/uint128.cpp
AABSPTree.hRendering/g3d/include/g3d/AABSPTree.h
AABox.hRendering/g3d/include/g3d/AABox.h
Array.hRendering/g3d/include/g3d/Array.h
BinaryFormat.hRendering/g3d/include/g3d/BinaryFormat.h
BinaryInput.hRendering/g3d/include/g3d/BinaryInput.h
BinaryOutput.hRendering/g3d/include/g3d/BinaryOutput.h
Box.hRendering/g3d/include/g3d/Box.h
Capsule.hRendering/g3d/include/g3d/Capsule.h
CollisionDetection.hRendering/g3d/include/g3d/CollisionDetection.h
Color1.hRendering/g3d/include/g3d/Color1.h
Color3.hRendering/g3d/include/g3d/Color3.h
Color3uint8.hRendering/g3d/include/g3d/Color3uint8.h
Color4.hRendering/g3d/include/g3d/Color4.h
Color4uint8.hRendering/g3d/include/g3d/Color4uint8.h
Cone.hRendering/g3d/include/g3d/Cone.h
ConvexPolyhedron.hRendering/g3d/include/g3d/ConvexPolyhedron.h
CoordinateFrame.hRendering/g3d/include/g3d/CoordinateFrame.h
Crypto.hRendering/g3d/include/g3d/Crypto.h
Cylinder.hRendering/g3d/include/g3d/Cylinder.h
EqualsTrait.hRendering/g3d/include/g3d/EqualsTrait.h
GCamera.hRendering/g3d/include/g3d/GCamera.h
GImage.hRendering/g3d/include/g3d/GImage.h
GLight.hRendering/g3d/include/g3d/GLight.h
HashTrait.hRendering/g3d/include/g3d/HashTrait.h
LightingParameters.hRendering/g3d/include/g3d/LightingParameters.h
Line.hRendering/g3d/include/g3d/Line.h
LineSegment.hRendering/g3d/include/g3d/LineSegment.h
Map2D.hRendering/g3d/include/g3d/Map2D.h
Matrix2.hRendering/g3d/include/g3d/Matrix2.h
Matrix3.hRendering/g3d/include/g3d/Matrix3.h
Matrix4.hRendering/g3d/include/g3d/Matrix4.h
MeshAlg.hRendering/g3d/include/g3d/MeshAlg.h
MeshBuilder.hRendering/g3d/include/g3d/MeshBuilder.h
ParseError.hRendering/g3d/include/g3d/ParseError.h
PhysicsFrame.hRendering/g3d/include/g3d/PhysicsFrame.h
Plane.hRendering/g3d/include/g3d/Plane.h
Quat.hRendering/g3d/include/g3d/Quat.h
Random.hRendering/g3d/include/g3d/Random.h
Ray.hRendering/g3d/include/g3d/Ray.h
Rect2D.hRendering/g3d/include/g3d/Rect2D.h
Set.hRendering/g3d/include/g3d/Set.h
SmallArray.hRendering/g3d/include/g3d/SmallArray.h
Sphere.hRendering/g3d/include/g3d/Sphere.h
System.hRendering/g3d/include/g3d/System.h
Table.hRendering/g3d/include/g3d/Table.h
Triangle.hRendering/g3d/include/g3d/Triangle.h
UprightFrame.hRendering/g3d/include/g3d/UprightFrame.h
Vector2.hRendering/g3d/include/g3d/Vector2.h
Vector2int16.hRendering/g3d/include/g3d/Vector2int16.h
Vector3.hRendering/g3d/include/g3d/Vector3.h
Vector3int16.hRendering/g3d/include/g3d/Vector3int16.h
Vector3int32.hRendering/g3d/include/g3d/Vector3int32.h
Vector4.hRendering/g3d/include/g3d/Vector4.h
Vector4int8.hRendering/g3d/include/g3d/Vector4int8.h
WrapMode.hRendering/g3d/include/g3d/WrapMode.h
constants.hRendering/g3d/include/g3d/constants.h
debug.hRendering/g3d/include/g3d/debug.h
enumclass.hRendering/g3d/include/g3d/enumclass.h
g3dmath.hRendering/g3d/include/g3d/g3dmath.h
platform.hRendering/g3d/include/g3d/platform.h
spline.hRendering/g3d/include/g3d/spline.h
stringutils.hRendering/g3d/include/g3d/stringutils.h
units.hRendering/g3d/include/g3d/units.h
vectorMath.hRendering/g3d/include/g3d/vectorMath.h
png.cRendering/g3d/png/png.c
pngerror.cRendering/g3d/png/pngerror.c
pnggccrd.cRendering/g3d/png/pnggccrd.c
pngget.cRendering/g3d/png/pngget.c
pngmem.cRendering/g3d/png/pngmem.c
pngpread.cRendering/g3d/png/pngpread.c
pngread.cRendering/g3d/png/pngread.c
pngrio.cRendering/g3d/png/pngrio.c
pngrtran.cRendering/g3d/png/pngrtran.c
pngrutil.cRendering/g3d/png/pngrutil.c
pngset.cRendering/g3d/png/pngset.c
pngtrans.cRendering/g3d/png/pngtrans.c
pngwio.cRendering/g3d/png/pngwio.c
pngwrite.cRendering/g3d/png/pngwrite.c
pngwutil.cRendering/g3d/png/pngwutil.c

Function Reference​

1. Draw::partAdorn​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Draw::partAdorn(const Part& part,
Adorn* adorn,
const G3D::Color3& controllerColor);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/Draw.cpp:17
SubsystemRendering Pipeline

How it Works Internally​

Executes partAdorn within Rendering Pipeline. Coordinates interactions with adornSurfaces.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: adornSurfaces.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on partAdorn.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


2. Draw::setSelectColor​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Draw::setSelectColor(const G3D::Color4& Color);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/Draw.cpp:29
SubsystemRendering Pipeline

How it Works Internally​

Set color used for the selection box when a part is selected.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Mutates internal member state or instance properties.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on setSelectColor.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


3. Draw::setHoverOverColor​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Draw::setHoverOverColor(const G3D::Color4& color);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/Draw.cpp:37
SubsystemRendering Pipeline

How it Works Internally​

Set the color used for the selection box when a part is mouse hover over.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Mutates internal member state or instance properties.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on setHoverOverColor.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


4. Draw::selectionBox​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Draw::selectionBox(const Part& part,
Adorn* adorn,
SelectState selectState,
float lineThickness);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/Draw.cpp:41
SubsystemRendering Pipeline

How it Works Internally​

Executes selectionBox within Rendering Pipeline. Coordinates interactions with setObjectToWorldMatrix, selectColor, orange.

  • Control Flow & Execution: Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: setObjectToWorldMatrix, selectColor, orange.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on selectionBox.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


5. Draw::selectionBox​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Draw::selectionBox(ModelInstance& model,
Adorn* adorn,
const G3D::Color4& selectColor,
float lineThickness);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/Draw.cpp:66
SubsystemRendering Pipeline

How it Works Internally​

Executes selectionBox within Rendering Pipeline. Coordinates interactions with computePart.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: computePart.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on selectionBox.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


6. Draw::adornSurfaces​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Draw::adornSurfaces(const Part& part,
Adorn* adorn,
const G3D::Color3& controllerColor);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/Draw.cpp:75
SubsystemRendering Pipeline

How it Works Internally​

Executes adornSurfaces within Rendering Pipeline. Coordinates interactions with constraint.

  • Control Flow & Execution: Iterative loop processing, Multi-case state dispatch.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: constraint.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on adornSurfaces.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


7. Draw::constraint​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Draw::constraint(const Part& part,
Adorn* adorn,
int face,
const G3D::Color3& controllerColor);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/Draw.cpp:90
SubsystemRendering Pipeline

How it Works Internally​

Executes constraint within Rendering Pipeline. Coordinates interactions with debugAssert, getAxisRotationMatrix, translation, setObjectToWorldMatrix.

  • Control Flow & Execution: Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: debugAssert, getAxisRotationMatrix, translation, setObjectToWorldMatrix, cylinderAlongX, yellow.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on constraint.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


8. Draw::selectionBox​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Draw::selectionBox(const Part& part,
Adorn* adorn,
const G3D::Color4& selectColor,
float lineThickness);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/Draw.cpp:127
SubsystemRendering Pipeline

How it Works Internally​

Executes selectionBox within Rendering Pipeline. Coordinates interactions with getCamera, getCameraCoordinateFrame, squaredLength, primaryAxis.

  • Control Flow & Execution: Iterative loop processing, Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Mutates internal member state or instance properties.
  • Key Internal Calls: getCamera, getCameraCoordinateFrame, squaredLength, primaryAxis, setObjectToWorldMatrix, outlineBox, Extents, box, AABox.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on selectionBox.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


9. DrawAdorn::cylinder​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::cylinder(Adorn* adorn,
const CoordinateFrame& worldC,
int axis,
float length,
float radius,
const Color4& color,
bool cap);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:57
SubsystemRendering Pipeline

How it Works Internally​

Executes cylinder within Rendering Pipeline. Coordinates interactions with getAxisRotationMatrix, rotatedWorldC, setObjectToWorldMatrix, cylinderAlongX.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: getAxisRotationMatrix, rotatedWorldC, setObjectToWorldMatrix, cylinderAlongX.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on cylinder.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


10. DrawAdorn::faceInWorld​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::faceInWorld(Adorn* adorn,
const Face& face,
float thickness,
const Color4& color);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:73
SubsystemRendering Pipeline

How it Works Internally​

Executes faceInWorld within Rendering Pipeline. Coordinates interactions with cross, setColumn, unit, setObjectToWorldMatrix.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: cross, setColumn, unit, setObjectToWorldMatrix, magnitude, extents, Vector3, box.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on faceInWorld.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


11. DrawAdorn::surfaceBorder​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::surfaceBorder(Adorn* adorn,
const Vector3& halfRealSize,
float highlight,
int surfaceId,
const Color4& color);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:101
SubsystemRendering Pipeline

How it Works Internally​

Executes surfaceBorder within Rendering Pipeline. Coordinates interactions with AABox, box.

  • Control Flow & Execution: Iterative loop processing.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: AABox, box.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on surfaceBorder.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


12. DrawAdorn::surfaceGridOnFace​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::surfaceGridOnFace(const Primitive& prim,
Adorn* adorn,
int surfaceId,
const Color4& color,
int boxesPerStud);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:132
SubsystemRendering Pipeline

How it Works Internally​

Executes surfaceGridOnFace within Rendering Pipeline. Coordinates interactions with getCoordinateFrame, getConstGeometry, getSurfaceCoordInBody, bounds.

  • Control Flow & Execution: Iterative loop processing, Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: getCoordinateFrame, getConstGeometry, getSurfaceCoordInBody, bounds, getNumVertsInSurface, getSurfaceVertInBody, pointToWorldSpace, pointToObjectSpace, surfaceGridAtCoord, unitX, unitY.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on surfaceGridOnFace.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


13. DrawAdorn::zeroPlaneGrid​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::zeroPlaneGrid(Adorn* adorn,
const RBX::Camera& camera,
const int studsPerBox,
const int yLevel,
const G3D::Color4& smallGridColor,
const G3D::Color4& largeGridColor);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:164
SubsystemRendering Pipeline

How it Works Internally​

Executes zeroPlaneGrid within Rendering Pipeline. Coordinates interactions with getCameraCoordinateFrame, Plane, Vector3, closestPoint.

  • Control Flow & Execution: Iterative loop processing, Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: getCameraCoordinateFrame, Plane, Vector3, closestPoint, iRound, magnitude, setObjectToWorldMatrix, zero, max, line3dAA, Color4, rgb.
  • External Library Dependencies: G3D Graphics and Math Engine.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on zeroPlaneGrid.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


14. DrawAdorn::surfaceGridAtCoord​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::surfaceGridAtCoord(Adorn* adorn,
CoordinateFrame& cF,
const Vector4& bounds,
const Vector3& gridXDir,
const Vector3& gridYDir,
const G3D::Color4& color,
int boxesPerStud);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:297
SubsystemRendering Pipeline

How it Works Internally​

Executes surfaceGridAtCoord within Rendering Pipeline. Coordinates interactions with iRound, fromDirectionCosines, cross, unitX.

  • Control Flow & Execution: Iterative loop processing, Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: iRound, fromDirectionCosines, cross, unitX, unitY, unitZ, zero, pointToWorldSpace, cylinder.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on surfaceGridAtCoord.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


15. DrawAdorn::axisWidget​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::axisWidget(Adorn* adorn, const RBX::Camera& camera);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:364
SubsystemRendering Pipeline

How it Works Internally​

Executes axisWidget within Rendering Pipeline. Coordinates interactions with getViewport, Vector3, width, height.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: getViewport, Vector3, width, height, getRenderingCoordinateFrame, lookVector, project, unitX, line2d, Vector2, drawFont2D, clear.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on axisWidget.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


16. DrawAdorn::circularGridAtCoord​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::circularGridAtCoord(Adorn* adorn,
const CoordinateFrame& coordFrame,
const G3D::Vector3& size,
const G3D::Vector3& cameraPos,
NormalId normalId,
const Color4& color,
int boxesPerStud);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:408
SubsystemRendering Pipeline

How it Works Internally​

Executes circularGridAtCoord within Rendering Pipeline. Coordinates interactions with Extents, handlePosInObject, pointToWorldSpace, length.

  • Control Flow & Execution: Iterative loop processing.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Mutates internal member state or instance properties.
  • Key Internal Calls: Extents, handlePosInObject, pointToWorldSpace, length, normalIdToVector3, pif, fromAxisAngle, scaleRelativeToCamera, setMaterial, cylinder.
  • External Library Dependencies: OpenGL / GLES Graphics API.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on circularGridAtCoord.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


17. DrawAdorn::lineSegmentRelativeToCoord​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::lineSegmentRelativeToCoord(Adorn* adorn,
const CoordinateFrame& cF,
const Vector3& pt0,
const Vector3& pt1,
const G3D::Color3& color,
float lineThickness);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:455
SubsystemRendering Pipeline

How it Works Internally​

Executes lineSegmentRelativeToCoord within Rendering Pipeline. Coordinates interactions with magnitude, getWellFormedRotForZVector, cylinder.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: magnitude, getWellFormedRotForZVector, cylinder.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on lineSegmentRelativeToCoord.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


18. DrawAdorn::verticalLineSegmentSplit​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::verticalLineSegmentSplit(Adorn* adorn,
const CoordinateFrame& cF,
const Vector3& pt0,
const Vector3& pt1,
const float& delta,
const float& dropFactor,
const short& level,
const G3D::Color3& color,
float lineThickness);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:473
SubsystemRendering Pipeline

How it Works Internally​

Executes verticalLineSegmentSplit within Rendering Pipeline. Coordinates interactions with lineSegmentRelativeToCoord.

  • Control Flow & Execution: Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: lineSegmentRelativeToCoord.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on verticalLineSegmentSplit.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


19. DrawAdorn::surfacePolygon​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::surfacePolygon(Adorn* adorn,
PartInstance& partInst,
int surfaceId,
const G3D::Color3& color,
float lineThickness);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:502
SubsystemRendering Pipeline

How it Works Internally​

Executes surfacePolygon within Rendering Pipeline. Coordinates interactions with getConstPrimitive, getConstGeometry, getNumVertsInSurface, push_back.

  • Control Flow & Execution: Iterative loop processing.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: getConstPrimitive, getConstGeometry, getNumVertsInSurface, push_back, getSurfaceVertInBody, polygonRelativeToCoord, getCoordinateFrame.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on surfacePolygon.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


20. DrawAdorn::polygonRelativeToCoord​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::polygonRelativeToCoord(Adorn* adorn,
const CoordinateFrame& cF,
std::vector<Vector3>& vertices,
const G3D::Color4& color,
float lineThickness);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:516
SubsystemRendering Pipeline

How it Works Internally​

Executes polygonRelativeToCoord within Rendering Pipeline. Coordinates interactions with size, magnitude, getWellFormedRotForZVector, cylinder.

  • Control Flow & Execution: Iterative loop processing.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: size, magnitude, getWellFormedRotForZVector, cylinder.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on polygonRelativeToCoord.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


21. DrawAdorn::partSurface​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::partSurface(const Part& part,
int surfaceId,
Adorn* adorn,
const Color4& color,
float thickness);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:537
SubsystemRendering Pipeline

How it Works Internally​

Executes partSurface within Rendering Pipeline. Coordinates interactions with setObjectToWorldMatrix, surfaceBorder.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: setObjectToWorldMatrix, surfaceBorder.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on partSurface.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


22. DrawAdorn::handlePosInObject​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

Vector3 DrawAdorn::handlePosInObject(const Vector3& cameraPos,
const Extents& localExtents,
HandleType handleType,
NormalId normalId);
PropertyValue
Return TypeVector3
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:551
SubsystemRendering Pipeline

How it Works Internally​

Executes handlePosInObject within Rendering Pipeline. Coordinates interactions with size, length, scaleRelativeToCamera, center.

  • Control Flow & Execution: Multi-case state dispatch, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Mutates internal member state or instance properties.
  • Key Internal Calls: size, length, scaleRelativeToCamera, center, normalIdToVector3, normalIdToU, start_offset, RBXASSERT, zero.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on handlePosInObject.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


23. DrawAdorn::scaleHandleRelativeToCamera​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

float DrawAdorn::scaleHandleRelativeToCamera(const Vector3& cameraPos,
HandleType handleType,
const Vector3& handlePos);
PropertyValue
Return Typefloat
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:600
SubsystemRendering Pipeline

How it Works Internally​

Executes scaleHandleRelativeToCamera within Rendering Pipeline. Coordinates interactions with scaleRelativeToCamera.

  • Control Flow & Execution: Multi-case state dispatch, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Mutates internal member state or instance properties.
  • Key Internal Calls: scaleRelativeToCamera.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on scaleHandleRelativeToCamera.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


24. DrawAdorn::scaleRelativeToCamera​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

float DrawAdorn::scaleRelativeToCamera(const Vector3& cameraPos,
const Vector3& handlePos,
float minAngle,
float expectedSize);
PropertyValue
Return Typefloat
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:637
SubsystemRendering Pipeline

How it Works Internally​

visual angle = radius/distance

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: magnitude.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on scaleRelativeToCamera.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


25. DrawAdorn::handles2d​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::handles2d(const G3D::Vector3& size,
const G3D::CoordinateFrame& position,
const RBX::Camera& camera,
Adorn* adorn,
HandleType handleType,
const G3D::Color4& color,
bool useAxisColor,
int normalIdMask);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:652
SubsystemRendering Pipeline

How it Works Internally​

Executes handles2d within Rendering Pipeline. Coordinates interactions with localExtents, handlePosInObject, coordinateFrame, pointToWorldSpace.

  • Control Flow & Execution: Iterative loop processing, Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: localExtents, handlePosInObject, coordinateFrame, pointToWorldSpace, scaleRelativeToCamera, normalIdToVector3, frame, project, infinity, rect2d, fromCenterSize, toRect2D.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on handles2d.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


26. DrawAdorn::partInfoText2D​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::partInfoText2D(const G3D::Vector3& size,
const G3D::CoordinateFrame& position,
const RBX::Camera& camera,
Adorn* adorn,
const std::string& text,
const G3D::Color4& color,
float fontSize,
int normalIdMask);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:708
SubsystemRendering Pipeline

How it Works Internally​

Executes partInfoText2D within Rendering Pipeline. Coordinates interactions with localExtents, max, min, Vector3.

  • Control Flow & Execution: Iterative loop processing, Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: localExtents, max, min, Vector3, Vector2, pointToWorldSpace, project, infinity, length, drawFont2D, clear.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on partInfoText2D.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


27. DrawAdorn::handles3d​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::handles3d(const G3D::Vector3& size,
const G3D::CoordinateFrame& position,
Adorn* adorn,
HandleType handleType,
const Vector3& cameraPos,
const G3D::Color4& color,
bool useAxisColor,
int normalIdMask,
NormalId normalIdTohighlight,
const G3D::Color4& highlightColor);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:787
SubsystemRendering Pipeline

How it Works Internally​

Executes handles3d within Rendering Pipeline. Coordinates interactions with localExtents, intToNormalId, handlePosInObject, pointToWorldSpace.

  • Control Flow & Execution: Iterative loop processing, Conditional branching, Multi-case state dispatch, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Mutates internal member state or instance properties.
  • Key Internal Calls: localExtents, intToNormalId, handlePosInObject, pointToWorldSpace, scaleHandleRelativeToCamera, frame, setObjectToWorldMatrix, setMaterial, sphere, Sphere, zero, normalIdToVector3.
  • External Library Dependencies: G3D Graphics and Math Engine.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on handles3d.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


28. eval​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

Vector3 eval(float t);
PropertyValue
Return TypeVector3
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:926
SubsystemRendering Pipeline

How it Works Internally​

Executes eval within Rendering Pipeline. Coordinates interactions with cos, sin.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: cos, sin.
  • External Library Dependencies: G3D Graphics and Math Engine.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on eval.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


29. evalTangent​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

Vector3 evalTangent(float t);
PropertyValue
Return TypeVector3
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:932
SubsystemRendering Pipeline

How it Works Internally​

first derivative.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: cos, sin.
  • External Library Dependencies: G3D Graphics and Math Engine.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on evalTangent.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


30. evalNormal​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

Vector3 evalNormal(float t);
PropertyValue
Return TypeVector3
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:937
SubsystemRendering Pipeline

How it Works Internally​

Executes evalNormal within Rendering Pipeline. Coordinates interactions with cos, sin.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: cos, sin.
  • External Library Dependencies: G3D Graphics and Math Engine.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on evalNormal.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


31. evalBinormal​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

Vector3 evalBinormal(float t);
PropertyValue
Return TypeVector3
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:942
SubsystemRendering Pipeline

How it Works Internally​

Executes evalBinormal within Rendering Pipeline.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on evalBinormal.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


32. hashString​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

std::string hashString();
PropertyValue
Return Typestd::string
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:948
SubsystemRendering Pipeline

How it Works Internally​

string that encodes this function in a unique way.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: CircleRN, str.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on hashString.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


33. DrawAdorn::chatBubble2d​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::chatBubble2d(Adorn* adorn,
const Rect2D& rect,
const G3D::Vector2 pointer,
float cornerradius,
const float linewidth,
const int quarterdivs,
const Color4& color);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:955
SubsystemRendering Pipeline

How it Works Internally​

Executes chatBubble2d within Rendering Pipeline. Coordinates interactions with min, width, height, center.

  • Control Flow & Execution: Iterative loop processing.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: min, width, height, center, push_back, Vector2, RBXASSERT, border, cos, sin, x1y1, x1y0.
  • External Library Dependencies: G3D Graphics and Math Engine.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on chatBubble2d.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


34. DrawAdorn::torus​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::torus(Adorn* adorn,
const CoordinateFrame& position,
NormalId axis,
float radius,
float thicknessradius,
const Color4& color);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:1036
SubsystemRendering Pipeline

How it Works Internally​

Executes torus within Rendering Pipeline. Coordinates interactions with trajectory, profile, setObjectToWorldMatrix, extrusion.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: trajectory, profile, setObjectToWorldMatrix, extrusion.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on torus.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


35. DrawAdorn::star​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::star(Adorn* adorn,
const Vector3& center,
float size,
const Color4& colorX,
const Color4& colorY,
const Color4& colorZ);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:1062
SubsystemRendering Pipeline

How it Works Internally​

Draws a wire star made up of 3 line segments. @param adorn object used to generate the geometry @param center world space center coordinates @param size lines are -size to +size on the axis @param colorX color of x axis line @param colorY color of y axis line @param colorZ color of z axis line

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: line3d, unitX, unitY, unitZ.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on star.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


36. DrawAdorn::outlineBox​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::outlineBox(Adorn* adorn,
const AABox& box,
const Color4& color);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:1093
SubsystemRendering Pipeline

How it Works Internally​

Draw an outline (wireframe) box in 3D. @param adorn adornment to use for drawing @param box box to draw @param color color of lines

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: low, high, line3d, Vector3.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on outlineBox.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


37. DrawAdorn::selectionBox​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DrawAdorn::selectionBox(Adorn* adorn,
const AABox& box,
const Color4& color);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/AppDraw/DrawAdorn.cpp:1167
SubsystemRendering Pipeline

How it Works Internally​

Draw select indicator around a box similar to 3DS. @param adorn adornment to use for drawing @param box box to draw @param color color of lines

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: low, high, line3d, Vector3.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on selectionBox.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


38. HitTest::hitTestBox​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool HitTest::hitTestBox(const Part& part,
RBX::RbxRay& rayInPartCoords,
Vector3& hitPointInPartCoords,
float gridToReal);
PropertyValue
Return Typebool
ModifiersNone
Source LocationRendering/AppDraw/HitTest.cpp:8
SubsystemRendering Pipeline

How it Works Internally​

Executes hitTestBox within Rendering Pipeline. Coordinates interactions with collisionLocationForMovingPointFixedAABox, origin, direction, AABox.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: collisionLocationForMovingPointFixedAABox, origin, direction, AABox.
  • External Library Dependencies: G3D Graphics and Math Engine.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on hitTestBox.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


39. HitTest::hitTestBall​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool HitTest::hitTestBall(const Part& part,
RBX::RbxRay& rayInPartCoords,
Vector3& hitPointInPartCoords,
float gridToReal);
PropertyValue
Return Typebool
ModifiersNone
Source LocationRendering/AppDraw/HitTest.cpp:22
SubsystemRendering Pipeline

How it Works Internally​

Executes hitTestBall within Rendering Pipeline. Coordinates interactions with return, collisionTimeForMovingPointFixedSphere, origin, direction.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: return, collisionTimeForMovingPointFixedSphere, origin, direction, Sphere, zero, inf.
  • External Library Dependencies: G3D Graphics and Math Engine.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on hitTestBall.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


40. HitTest::hitTestCylinder​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool HitTest::hitTestCylinder(const Part& part,
RBX::RbxRay& rayInPartCoords,
Vector3& hitPointInPartCoords,
float gridToReal);
PropertyValue
Return Typebool
ModifiersNone
Source LocationRendering/AppDraw/HitTest.cpp:42
SubsystemRendering Pipeline

How it Works Internally​

TODO: Big optimization possible here... TODO: Clean up hit test here - offset stuff going on

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: return, collisionTimeForMovingPointFixedCapsule, origin, direction, Capsule, zero, Vector3, inf.
  • External Library Dependencies: G3D Graphics and Math Engine.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on hitTestCylinder.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


41. HitTest::hitTest​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool HitTest::hitTest(const Part& part,
RBX::RbxRay& rayInPartCoords,
Vector3& hitPointInPartCoords,
float gridToReal);
PropertyValue
Return Typebool
ModifiersNone
Source LocationRendering/AppDraw/HitTest.cpp:58
SubsystemRendering Pipeline

How it Works Internally​

Executes hitTest within Rendering Pipeline. Coordinates interactions with hitTestBox, hitTestBall, hitTestCylinder, debugAssert.

  • Control Flow & Execution: Multi-case state dispatch, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: hitTestBox, hitTestBall, hitTestCylinder, debugAssert.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on hitTest.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


42. selectColor​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

G3D::Color4& selectColor() const;
PropertyValue
Return TypeG3D::Color4&
Modifiersstatic const
Source LocationRendering/AppDraw/include/appdraw/Draw.h:38
SubsystemRendering Pipeline

How it Works Internally​

Executes selectColor within Rendering Pipeline.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on selectColor.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


43. hoverOverColor​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

G3D::Color4& hoverOverColor() const;
PropertyValue
Return TypeG3D::Color4&
Modifiersstatic const
Source LocationRendering/AppDraw/include/appdraw/Draw.h:40
SubsystemRendering Pipeline

How it Works Internally​

Executes hoverOverColor within Rendering Pipeline.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on hoverOverColor.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


44. showHoverOver​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void showHoverOver(bool Show);
PropertyValue
Return Typevoid
Modifiersstatic
Source LocationRendering/AppDraw/include/appdraw/Draw.h:69
SubsystemRendering Pipeline

How it Works Internally​

Executes showHoverOver within Rendering Pipeline.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Mutates internal member state or instance properties.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on showHoverOver.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


45. isHoverOver​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool isHoverOver();
PropertyValue
Return Typebool
Modifiersstatic
Source LocationRendering/AppDraw/include/appdraw/Draw.h:71
SubsystemRendering Pipeline

How it Works Internally​

Executes isHoverOver within Rendering Pipeline.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on isHoverOver.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


46. resizeColor​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

Color3& resizeColor() const;
PropertyValue
Return TypeColor3&
Modifiersstatic const
Source LocationRendering/AppDraw/include/appdraw/DrawAdorn.h:29
SubsystemRendering Pipeline

How it Works Internally​

Executes resizeColor within Rendering Pipeline.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on resizeColor.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


47. outlineBox​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void outlineBox(Adorn* adorn,
const Extents& extents,
const Color4& color);
PropertyValue
Return Typevoid
Modifiersstatic
Source LocationRendering/AppDraw/include/appdraw/DrawAdorn.h:226
SubsystemRendering Pipeline

How it Works Internally​

Draw an outline (wireframe) box in 3D. @param adorn adornment to use for drawing @param extents box dimensions @param color color of lines

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: aa_box, min, max.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on outlineBox.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


48. selectionBox​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void selectionBox(Adorn* adorn,
const Extents& extents,
const Color4& color);
PropertyValue
Return Typevoid
Modifiersstatic
Source LocationRendering/AppDraw/include/appdraw/DrawAdorn.h:254
SubsystemRendering Pipeline

How it Works Internally​

Draw select indicator around a box similar to 3DS. @param adorn adornment to use for drawing @param extents box dimensions @param color color of lines

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: aa_box, min, max.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on selectionBox.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


49. outlineRect2dImpl​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void outlineRect2dImpl(Adorn* adorn, const Rect2D& rect, float thick, const Color4& color, const Modifier& modifier);
PropertyValue
Return Typevoid
Modifiersstatic
Source LocationRendering/GfxBase/Adorn.cpp:3
SubsystemRendering Pipeline

How it Works Internally​

Executes outlineRect2dImpl within Rendering Pipeline. Coordinates interactions with rect2d, xyxy.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: rect2d, xyxy.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on outlineRect2dImpl.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


50. Adorn::outlineRect2d​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Adorn::outlineRect2d(const Rect2D& rect, float thick, const Color4& color);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/GfxBase/Adorn.cpp:13
SubsystemRendering Pipeline

How it Works Internally​

Executes outlineRect2d within Rendering Pipeline. Coordinates interactions with outlineRect2dImpl, Rotation2D.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: outlineRect2dImpl, Rotation2D.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on outlineRect2d.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


51. Adorn::outlineRect2d​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Adorn::outlineRect2d(const Rect2D& rect, float thick, const Color4& color, const Rotation2D& rotation);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/GfxBase/Adorn.cpp:18
SubsystemRendering Pipeline

How it Works Internally​

Executes outlineRect2d within Rendering Pipeline. Coordinates interactions with outlineRect2dImpl.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: outlineRect2dImpl.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on outlineRect2d.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


52. Adorn::outlineRect2d​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Adorn::outlineRect2d(const Rect2D& rect, float thick, const Color4& color, const Rect2D& clipRect);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/GfxBase/Adorn.cpp:23
SubsystemRendering Pipeline

How it Works Internally​

Executes outlineRect2d within Rendering Pipeline. Coordinates interactions with outlineRect2dImpl.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: outlineRect2dImpl.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on outlineRect2d.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


53. Adorn::rect2d​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Adorn::rect2d(const Rect2D& rect, const Color4& color);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/GfxBase/Adorn.cpp:28
SubsystemRendering Pipeline

How it Works Internally​

Executes rect2d within Rendering Pipeline. Coordinates interactions with Vector2, Rotation2D.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: Vector2, Rotation2D.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on rect2d.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


54. Adorn::rect2d​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Adorn::rect2d(const Rect2D& rect, const Color4& color, const Rotation2D& rotation);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/GfxBase/Adorn.cpp:33
SubsystemRendering Pipeline

How it Works Internally​

Executes rect2d within Rendering Pipeline. Coordinates interactions with Vector2.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: Vector2.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on rect2d.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


55. Adorn::rect2d​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Adorn::rect2d(const Rect2D& rect, const Color4& color, const Rect2D& clipRect);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/GfxBase/Adorn.cpp:38
SubsystemRendering Pipeline

How it Works Internally​

Executes rect2d within Rendering Pipeline. Coordinates interactions with Vector2.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: Vector2.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on rect2d.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


56. Adorn::rect2d​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Adorn::rect2d(const Rect2D& rect, const Vector2& texul, const Vector2& texbr, const Color4& color);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/GfxBase/Adorn.cpp:43
SubsystemRendering Pipeline

How it Works Internally​

Executes rect2d within Rendering Pipeline. Coordinates interactions with Rotation2D.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: Rotation2D.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on rect2d.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


57. Adorn::rect2d​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Adorn::rect2d(const Rect2D& rect, const Vector2& texul, const Vector2& texbr, const Color4& color, const Rotation2D& rotation);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/GfxBase/Adorn.cpp:48
SubsystemRendering Pipeline

How it Works Internally​

Executes rect2d within Rendering Pipeline. Coordinates interactions with empty, rotate, x0y0, x1y0.

  • Control Flow & Execution: Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: empty, rotate, x0y0, x1y0, x0y1, x1y1, rect2dImpl.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on rect2d.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


58. Adorn::rect2d​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Adorn::rect2d(const Rect2D& rect, const Vector2& texul, const Vector2& texbr, const Color4& color, const Rect2D& clipRect);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationRendering/GfxBase/Adorn.cpp:65
SubsystemRendering Pipeline

How it Works Internally​

Executes rect2d within Rendering Pipeline. Coordinates interactions with lowerUV, upperUV, intersect, width.

  • Control Flow & Execution: Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: lowerUV, upperUV, intersect, width, height, rect2dImpl, x0y0, x1y0, x0y1, x1y1.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on rect2d.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


59. Adorn::drawFont2D​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

Vector2 Adorn::drawFont2D(const std::string& s,
const Vector2& position, float size, bool autoScale, const Color4& color, const Color4& outline,
Text::Font font, Text::XAlign xalign, Text::YAlign yalign,
const Vector2& availableSpace, const Rect2D& clippingRect, const Rotation2D& rotation);
PropertyValue
Return TypeVector2
ModifiersNone
Source LocationRendering/GfxBase/Adorn.cpp:96
SubsystemRendering Pipeline

How it Works Internally​

Executes drawFont2D within Rendering Pipeline. Coordinates interactions with drawFont2DImpl.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: drawFont2DImpl.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on drawFont2D.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


60. AdornBillboarder::getViewport​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

Rect2D AdornBillboarder::getViewport() const;
PropertyValue
Return TypeRect2D
Modifiersconst
Source LocationRendering/GfxBase/AdornBillboarder.cpp:21
SubsystemRendering Pipeline

How it Works Internally​

Executes getViewport within Rendering Pipeline.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on getViewport.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


Additional Functions

There are 6205 additional internal and inline functions in this subsystem. All functions are indexed and cross-referenced in the Complete Function Catalog.