Skip to main content

App - DataModel & Hierarchy

Engine DataModel hierarchy, Workspace, Players, Instances, and Services.

Subsystem Metrics​

  • Total Documented Functions: 4683
  • Functions Exercised in Tests: 266
  • Platform-Divergent Implementations: 280
  • Component Source Files: 342

Source Files​

View all 342 source files in this subsystem
Source FilePath
Accoutrement.hApp/include/v8datamodel/Accoutrement.h
ActionStation.hApp/include/v8datamodel/ActionStation.h
Adornment.hApp/include/v8datamodel/Adornment.h
AnimatableRootJoint.hApp/include/v8datamodel/AnimatableRootJoint.h
Animation.hApp/include/v8datamodel/Animation.h
AnimationTrackState.hApp/include/v8datamodel/AnimationTrackState.h
Animator.hApp/include/v8datamodel/Animator.h
ArcHandles.hApp/include/v8datamodel/ArcHandles.h
Attachment.hApp/include/v8datamodel/Attachment.h
BasicPartInstance.hApp/include/v8datamodel/BasicPartInstance.h
BillboardGui.hApp/include/v8datamodel/BillboardGui.h
BlockMesh.hApp/include/v8datamodel/BlockMesh.h
CSGMesh.hApp/include/v8datamodel/CSGMesh.h
CacheableContentProvider.hApp/include/v8datamodel/CacheableContentProvider.h
Camera.hApp/include/v8datamodel/Camera.h
ChangeHistory.hApp/include/v8datamodel/ChangeHistory.h
CharacterAppearance.hApp/include/v8datamodel/CharacterAppearance.h
CharacterMesh.hApp/include/v8datamodel/CharacterMesh.h
ClickDetector.hApp/include/v8datamodel/ClickDetector.h
CollectionService.hApp/include/v8datamodel/CollectionService.h
ColorSequence.hApp/include/v8datamodel/ColorSequence.h
Commands.hApp/include/v8datamodel/Commands.h
ContentProvider.hApp/include/v8datamodel/ContentProvider.h
CustomEvent.hApp/include/v8datamodel/CustomEvent.h
CustomEventReceiver.hApp/include/v8datamodel/CustomEventReceiver.h
CustomParticleEmitter.hApp/include/v8datamodel/CustomParticleEmitter.h
CylinderMesh.hApp/include/v8datamodel/CylinderMesh.h
DataModel.hApp/include/v8datamodel/DataModel.h
DataModelMesh.hApp/include/v8datamodel/DataModelMesh.h
DataStore.hApp/include/v8datamodel/DataStore.h
DataStoreService.hApp/include/v8datamodel/DataStoreService.h
DebrisService.hApp/include/v8datamodel/DebrisService.h
DebugSettings.hApp/include/v8datamodel/DebugSettings.h
Decal.hApp/include/v8datamodel/Decal.h
DialogChoice.hApp/include/v8datamodel/DialogChoice.h
DialogRoot.hApp/include/v8datamodel/DialogRoot.h
EventReplicator.hApp/include/v8datamodel/EventReplicator.h
Explosion.hApp/include/v8datamodel/Explosion.h
ExtrudedPartInstance.hApp/include/v8datamodel/ExtrudedPartInstance.h
FaceInstance.hApp/include/v8datamodel/FaceInstance.h
Feature.hApp/include/v8datamodel/Feature.h
FileMesh.hApp/include/v8datamodel/FileMesh.h
Filters.hApp/include/v8datamodel/Filters.h
Fire.hApp/include/v8datamodel/Fire.h
Flag.hApp/include/v8datamodel/Flag.h
FlyweightService.hApp/include/v8datamodel/FlyweightService.h
ForceField.hApp/include/v8datamodel/ForceField.h
Frame.hApp/include/v8datamodel/Frame.h
FriendService.hApp/include/v8datamodel/FriendService.h
Game.hApp/include/v8datamodel/Game.h
GameBasicSettings.hApp/include/v8datamodel/GameBasicSettings.h
GameSettings.hApp/include/v8datamodel/GameSettings.h
GamepadService.hApp/include/v8datamodel/GamepadService.h
GlobalSettings.hApp/include/v8datamodel/GlobalSettings.h
GuiBase.hApp/include/v8datamodel/GuiBase.h
GuiBase2d.hApp/include/v8datamodel/GuiBase2d.h
GuiBase3d.hApp/include/v8datamodel/GuiBase3d.h
GuiBuilder.hApp/include/v8datamodel/GuiBuilder.h
GuiLayerCollector.hApp/include/v8datamodel/GuiLayerCollector.h
GuiMixin.hApp/include/v8datamodel/GuiMixin.h
GuiObject.hApp/include/v8datamodel/GuiObject.h
GuiService.hApp/include/v8datamodel/GuiService.h
GuiText.hApp/include/v8datamodel/GuiText.h
Gyro.hApp/include/v8datamodel/Gyro.h
HackDefines.hApp/include/v8datamodel/HackDefines.h
HandleAdornment.hApp/include/v8datamodel/HandleAdornment.h
Handles.hApp/include/v8datamodel/Handles.h
HandlesBase.hApp/include/v8datamodel/HandlesBase.h
Hopper.hApp/include/v8datamodel/Hopper.h
HttpRbxApiJob.hApp/include/v8datamodel/HttpRbxApiJob.h
HttpRbxApiService.hApp/include/v8datamodel/HttpRbxApiService.h
IAnimatableJoint.hApp/include/v8datamodel/IAnimatableJoint.h
ICameraOwner.hApp/include/v8datamodel/ICameraOwner.h
ICharacterSubject.hApp/include/v8datamodel/ICharacterSubject.h
IModelModifier.hApp/include/v8datamodel/IModelModifier.h
ImageButton.hApp/include/v8datamodel/ImageButton.h
InputObject.hApp/include/v8datamodel/InputObject.h
InsertService.hApp/include/v8datamodel/InsertService.h
JointInstance.hApp/include/v8datamodel/JointInstance.h
Keyframe.hApp/include/v8datamodel/Keyframe.h
KeyframeSequence.hApp/include/v8datamodel/KeyframeSequence.h
Light.hApp/include/v8datamodel/Light.h
Lighting.hApp/include/v8datamodel/Lighting.h
ManualJointHelper.hApp/include/v8datamodel/ManualJointHelper.h
MarketplaceService.hApp/include/v8datamodel/MarketplaceService.h
MegaCluster.hApp/include/v8datamodel/MegaCluster.h
ModelInstance.hApp/include/v8datamodel/ModelInstance.h
Mouse.hApp/include/v8datamodel/Mouse.h
MouseCommand.hApp/include/v8datamodel/MouseCommand.h
NumberSequence.hApp/include/v8datamodel/NumberSequence.h
PVInstance.hApp/include/v8datamodel/PVInstance.h
ParametricPartInstance.hApp/include/v8datamodel/ParametricPartInstance.h
PartCookie.hApp/include/v8datamodel/PartCookie.h
PartInstance.hApp/include/v8datamodel/PartInstance.h
PartOperation.hApp/include/v8datamodel/PartOperation.h
PartOperationAsset.hApp/include/v8datamodel/PartOperationAsset.h
PathfindingService.hApp/include/v8datamodel/PathfindingService.h
PersonalServerService.hApp/include/v8datamodel/PersonalServerService.h
PhysicsInstructions.hApp/include/v8datamodel/PhysicsInstructions.h
PhysicsService.hApp/include/v8datamodel/PhysicsService.h
PhysicsSettings.hApp/include/v8datamodel/PhysicsSettings.h
Platform.hApp/include/v8datamodel/Platform.h
PlayerGui.hApp/include/v8datamodel/PlayerGui.h
PlayerScripts.hApp/include/v8datamodel/PlayerScripts.h
PluginManager.hApp/include/v8datamodel/PluginManager.h
Pose.hApp/include/v8datamodel/Pose.h
PostEffect.hApp/include/v8datamodel/PostEffect.h
Remote.hApp/include/v8datamodel/Remote.h
RenderHooksService.hApp/include/v8datamodel/RenderHooksService.h
ReplicatedFirst.hApp/include/v8datamodel/ReplicatedFirst.h
RootInstance.hApp/include/v8datamodel/RootInstance.h
SafeChat.hApp/include/v8datamodel/SafeChat.h
Scale9Frame.hApp/include/v8datamodel/Scale9Frame.h
ScreenGui.hApp/include/v8datamodel/ScreenGui.h
ScriptMouseCommand.hApp/include/v8datamodel/ScriptMouseCommand.h
ScrollingFrame.hApp/include/v8datamodel/ScrollingFrame.h
Seat.hApp/include/v8datamodel/Seat.h
Selection.hApp/include/v8datamodel/Selection.h
SelectionBox.hApp/include/v8datamodel/SelectionBox.h
SelectionLasso.hApp/include/v8datamodel/SelectionLasso.h
SelectionSphere.hApp/include/v8datamodel/SelectionSphere.h
ServerScriptService.hApp/include/v8datamodel/ServerScriptService.h
SkateboardController.hApp/include/v8datamodel/SkateboardController.h
SkateboardPlatform.hApp/include/v8datamodel/SkateboardPlatform.h
Sky.hApp/include/v8datamodel/Sky.h
Smoke.hApp/include/v8datamodel/Smoke.h
Sparkles.hApp/include/v8datamodel/Sparkles.h
SpawnLocation.hApp/include/v8datamodel/SpawnLocation.h
SpecialMesh.hApp/include/v8datamodel/SpecialMesh.h
StarterPlayerService.hApp/include/v8datamodel/StarterPlayerService.h
Stats.hApp/include/v8datamodel/Stats.h
StudioTool.hApp/include/v8datamodel/StudioTool.h
StudioToolMouseCommand.hApp/include/v8datamodel/StudioToolMouseCommand.h
Surface.hApp/include/v8datamodel/Surface.h
SurfaceGui.hApp/include/v8datamodel/SurfaceGui.h
SurfaceSelection.hApp/include/v8datamodel/SurfaceSelection.h
Teams.hApp/include/v8datamodel/Teams.h
TeleportCallback.hApp/include/v8datamodel/TeleportCallback.h
TeleportService.hApp/include/v8datamodel/TeleportService.h
TerrainRegion.hApp/include/v8datamodel/TerrainRegion.h
Test.hApp/include/v8datamodel/Test.h
TextBox.hApp/include/v8datamodel/TextBox.h
Tool.hApp/include/v8datamodel/Tool.h
ToolsPart.hApp/include/v8datamodel/ToolsPart.h
UserController.hApp/include/v8datamodel/UserController.h
UserInputService.hApp/include/v8datamodel/UserInputService.h
Value.hApp/include/v8datamodel/Value.h
VehicleSeat.hApp/include/v8datamodel/VehicleSeat.h
Visit.hApp/include/v8datamodel/Visit.h
Workspace.hApp/include/v8datamodel/Workspace.h
Accoutrement.cppApp/v8datamodel/Accoutrement.cpp
AdService.cppApp/v8datamodel/AdService.cpp
Adornment.cppApp/v8datamodel/Adornment.cpp
AnimatableRootJoint.cppApp/v8datamodel/AnimatableRootJoint.cpp
Animation.cppApp/v8datamodel/Animation.cpp
AnimationController.cppApp/v8datamodel/AnimationController.cpp
AnimationTrack.cppApp/v8datamodel/AnimationTrack.cpp
AnimationTrackState.cppApp/v8datamodel/AnimationTrackState.cpp
Animator.cppApp/v8datamodel/Animator.cpp
ArcHandles.cppApp/v8datamodel/ArcHandles.cpp
AssetService.cppApp/v8datamodel/AssetService.cpp
Attachment.cppApp/v8datamodel/Attachment.cpp
Backpack.cppApp/v8datamodel/Backpack.cpp
BadgeService.cppApp/v8datamodel/BadgeService.cpp
BaseRenderJob.cppApp/v8datamodel/BaseRenderJob.cpp
BasicPartInstance.cppApp/v8datamodel/BasicPartInstance.cpp
BevelMesh.cppApp/v8datamodel/BevelMesh.cpp
BillboardGui.cppApp/v8datamodel/BillboardGui.cpp
Bindable.cppApp/v8datamodel/Bindable.cpp
CSGDictionaryService.cppApp/v8datamodel/CSGDictionaryService.cpp
CSGMesh.cppApp/v8datamodel/CSGMesh.cpp
Camera.cppApp/v8datamodel/Camera.cpp
ChangeHistory.cppApp/v8datamodel/ChangeHistory.cpp
CharacterAppearance.cppApp/v8datamodel/CharacterAppearance.cpp
CharacterMesh.cppApp/v8datamodel/CharacterMesh.cpp
ChatService.cppApp/v8datamodel/ChatService.cpp
ClickDetector.cppApp/v8datamodel/ClickDetector.cpp
CollectionService.cppApp/v8datamodel/CollectionService.cpp
ColorSequence.cppApp/v8datamodel/ColorSequence.cpp
Commands.cppApp/v8datamodel/Commands.cpp
Configuration.cppApp/v8datamodel/Configuration.cpp
ContextActionService.cppApp/v8datamodel/ContextActionService.cpp
CookiesEngineService.cppApp/v8datamodel/CookiesEngineService.cpp
CustomEventReceiver.cppApp/v8datamodel/CustomEventReceiver.cpp
CustomParticleEmitter.cppApp/v8datamodel/CustomParticleEmitter.cpp
DataModel.cppApp/v8datamodel/DataModel.cpp
DataModelJob.cppApp/v8datamodel/DataModelJob.cpp
DataModelMesh.cppApp/v8datamodel/DataModelMesh.cpp
DataStore.cppApp/v8datamodel/DataStore.cpp
DataStoreService.cppApp/v8datamodel/DataStoreService.cpp
DebrisService.cppApp/v8datamodel/DebrisService.cpp
DebugSettings.cppApp/v8datamodel/DebugSettings.cpp
Decal.cppApp/v8datamodel/Decal.cpp
DialogChoice.cppApp/v8datamodel/DialogChoice.cpp
DialogRoot.cppApp/v8datamodel/DialogRoot.cpp
Explosion.cppApp/v8datamodel/Explosion.cpp
ExtrudedPartInstance.cppApp/v8datamodel/ExtrudedPartInstance.cpp
FaceInstance.cppApp/v8datamodel/FaceInstance.cpp
FastLogSettings.cppApp/v8datamodel/FastLogSettings.cpp
Feature.cppApp/v8datamodel/Feature.cpp
FileMesh.cppApp/v8datamodel/FileMesh.cpp
Filters.cppApp/v8datamodel/Filters.cpp
Fire.cppApp/v8datamodel/Fire.cpp
Flag.cppApp/v8datamodel/Flag.cpp
FlagStand.cppApp/v8datamodel/FlagStand.cpp
FloorWire.cppApp/v8datamodel/FloorWire.cpp
FlyweightService.cppApp/v8datamodel/FlyweightService.cpp
Folder.cppApp/v8datamodel/Folder.cpp
ForceField.cppApp/v8datamodel/ForceField.cpp
Frame.cppApp/v8datamodel/Frame.cpp
FriendService.cppApp/v8datamodel/FriendService.cpp
Game.cppApp/v8datamodel/Game.cpp
GameBasicSettings.cppApp/v8datamodel/GameBasicSettings.cpp
GamePassService.cppApp/v8datamodel/GamePassService.cpp
GameSettings.cppApp/v8datamodel/GameSettings.cpp
GamepadService.cppApp/v8datamodel/GamepadService.cpp
GeometryService.cppApp/v8datamodel/GeometryService.cpp
GlobalSettings.cppApp/v8datamodel/GlobalSettings.cpp
GuiBase.cppApp/v8datamodel/GuiBase.cpp
GuiBase2d.cppApp/v8datamodel/GuiBase2d.cpp
GuiBase3d.cppApp/v8datamodel/GuiBase3d.cpp
GuiBuilder.cppApp/v8datamodel/GuiBuilder.cpp
GuiLayerCollector.cppApp/v8datamodel/GuiLayerCollector.cpp
GuiObject.cppApp/v8datamodel/GuiObject.cpp
GuiService.cppApp/v8datamodel/GuiService.cpp
Gyro.cppApp/v8datamodel/Gyro.cpp
HandleAdornment.cppApp/v8datamodel/HandleAdornment.cpp
Handles.cppApp/v8datamodel/Handles.cpp
HandlesBase.cppApp/v8datamodel/HandlesBase.cpp
HapticService.cppApp/v8datamodel/HapticService.cpp
Hopper.cppApp/v8datamodel/Hopper.cpp
HttpRbxApiService.cppApp/v8datamodel/HttpRbxApiService.cpp
HttpService.cppApp/v8datamodel/HttpService.cpp
ICharacterSubject.cppApp/v8datamodel/ICharacterSubject.cpp
IEquipable.cppApp/v8datamodel/IEquipable.cpp
ImageButton.cppApp/v8datamodel/ImageButton.cpp
ImageLabel.cppApp/v8datamodel/ImageLabel.cpp
InputObject.cppApp/v8datamodel/InputObject.cpp
InsertService.cppApp/v8datamodel/InsertService.cpp
JointInstance.cppApp/v8datamodel/JointInstance.cpp
JointsService.cppApp/v8datamodel/JointsService.cpp
Keyframe.cppApp/v8datamodel/Keyframe.cpp
KeyframeSequence.cppApp/v8datamodel/KeyframeSequence.cpp
KeyframeSequenceProvider.cppApp/v8datamodel/KeyframeSequenceProvider.cpp
Light.cppApp/v8datamodel/Light.cpp
Lighting.cppApp/v8datamodel/Lighting.cpp
LogService.cppApp/v8datamodel/LogService.cpp
LoginService.cppApp/v8datamodel/LoginService.cpp
ManualJointHelper.cppApp/v8datamodel/ManualJointHelper.cpp
MarketplaceService.cppApp/v8datamodel/MarketplaceService.cpp
MegaCluster.cppApp/v8datamodel/MegaCluster.cpp
Message.cppApp/v8datamodel/Message.cpp
ModelInstance.cppApp/v8datamodel/ModelInstance.cpp
Mouse.cppApp/v8datamodel/Mouse.cpp
MouseCommand.cppApp/v8datamodel/MouseCommand.cpp
NonReplicatedCSGDictionaryService.cppApp/v8datamodel/NonReplicatedCSGDictionaryService.cpp
NotificationService.cppApp/v8datamodel/NotificationService.cpp
NumberRange.cppApp/v8datamodel/NumberRange.cpp
NumberSequence.cppApp/v8datamodel/NumberSequence.cpp
PVInstance.cppApp/v8datamodel/PVInstance.cpp
PartCookie.cppApp/v8datamodel/PartCookie.cpp
PartInstance.cppApp/v8datamodel/PartInstance.cpp
PartOperation.cppApp/v8datamodel/PartOperation.cpp
PartOperationAsset.cppApp/v8datamodel/PartOperationAsset.cpp
PathfindingService.cppApp/v8datamodel/PathfindingService.cpp
PersonalServerService.cppApp/v8datamodel/PersonalServerService.cpp
PhysicsInstructions.cppApp/v8datamodel/PhysicsInstructions.cpp
PhysicsService.cppApp/v8datamodel/PhysicsService.cpp
PhysicsSettings.cppApp/v8datamodel/PhysicsSettings.cpp
Platform.cppApp/v8datamodel/Platform.cpp
PlatformService.cppApp/v8datamodel/PlatformService.cpp
PlayerGui.cppApp/v8datamodel/PlayerGui.cpp
PlayerMouse.cppApp/v8datamodel/PlayerMouse.cpp
PlayerScripts.cppApp/v8datamodel/PlayerScripts.cpp
PluginManager.cppApp/v8datamodel/PluginManager.cpp
PluginMouse.cppApp/v8datamodel/PluginMouse.cpp
PointsService.cppApp/v8datamodel/PointsService.cpp
Pose.cppApp/v8datamodel/Pose.cpp
PostEffect.cppApp/v8datamodel/PostEffect.cpp
PrismInstance.cppApp/v8datamodel/PrismInstance.cpp
PyramidInstance.cppApp/v8datamodel/PyramidInstance.cpp
Remote.cppApp/v8datamodel/Remote.cpp
RenderHooksService.cppApp/v8datamodel/RenderHooksService.cpp
ReplicatedFirst.cppApp/v8datamodel/ReplicatedFirst.cpp
RootInstance.cppApp/v8datamodel/RootInstance.cpp
SafeChat.cppApp/v8datamodel/SafeChat.cpp
Scale9Frame.cppApp/v8datamodel/Scale9Frame.cpp
ScreenGui.cppApp/v8datamodel/ScreenGui.cpp
ScriptMouseCommand.cppApp/v8datamodel/ScriptMouseCommand.cpp
ScrollingFrame.cppApp/v8datamodel/ScrollingFrame.cpp
Seat.cppApp/v8datamodel/Seat.cpp
Selection.cppApp/v8datamodel/Selection.cpp
SelectionBox.cppApp/v8datamodel/SelectionBox.cpp
SelectionLasso.cppApp/v8datamodel/SelectionLasso.cpp
SelectionSphere.cppApp/v8datamodel/SelectionSphere.cpp
ServerScriptService.cppApp/v8datamodel/ServerScriptService.cpp
ServerStorage.cppApp/v8datamodel/ServerStorage.cpp
SkateboardController.cppApp/v8datamodel/SkateboardController.cpp
SkateboardPlatform.cppApp/v8datamodel/SkateboardPlatform.cpp
Sky.cppApp/v8datamodel/Sky.cpp
SleepingJob.cppApp/v8datamodel/SleepingJob.cpp
Smoke.cppApp/v8datamodel/Smoke.cpp
SocialService.cppApp/v8datamodel/SocialService.cpp
SolidModelContentProvider.cppApp/v8datamodel/SolidModelContentProvider.cpp
Sparkles.cppApp/v8datamodel/Sparkles.cpp
SpawnLocation.cppApp/v8datamodel/SpawnLocation.cpp
SpecialMesh.cppApp/v8datamodel/SpecialMesh.cpp
StarterPlayerService.cppApp/v8datamodel/StarterPlayerService.cpp
Stats.cppApp/v8datamodel/Stats.cpp
StudioTool.cppApp/v8datamodel/StudioTool.cpp
StudioToolMouseCommand.cppApp/v8datamodel/StudioToolMouseCommand.cpp
StudioToolVerb.cppApp/v8datamodel/StudioToolVerb.cpp
Surface.cppApp/v8datamodel/Surface.cpp
SurfaceGui.cppApp/v8datamodel/SurfaceGui.cpp
SurfaceSelection.cppApp/v8datamodel/SurfaceSelection.cpp
Team.cppApp/v8datamodel/Team.cpp
Teams.cppApp/v8datamodel/Teams.cpp
TeleportService.cppApp/v8datamodel/TeleportService.cpp
TerrainRegion.cppApp/v8datamodel/TerrainRegion.cpp
Test.cppApp/v8datamodel/Test.cpp
TextBox.cppApp/v8datamodel/TextBox.cpp
TextButton.cppApp/v8datamodel/TextButton.cpp
TextLabel.cppApp/v8datamodel/TextLabel.cpp
TextService.cppApp/v8datamodel/TextService.cpp
TextureTrail.cppApp/v8datamodel/TextureTrail.cpp
TimerService.cppApp/v8datamodel/TimerService.cpp
Tool.cppApp/v8datamodel/Tool.cpp
ToolMouseCommand.cppApp/v8datamodel/ToolMouseCommand.cpp
ToolsModel.cppApp/v8datamodel/ToolsModel.cpp
ToolsPart.cppApp/v8datamodel/ToolsPart.cpp
ToolsSurface.cppApp/v8datamodel/ToolsSurface.cpp
TouchInputService.cppApp/v8datamodel/TouchInputService.cpp
TouchTransmitter.cppApp/v8datamodel/TouchTransmitter.cpp
TweenService.cppApp/v8datamodel/TweenService.cpp
UserController.cppApp/v8datamodel/UserController.cpp
UserInputService.cppApp/v8datamodel/UserInputService.cpp
Value.cppApp/v8datamodel/Value.cpp
VehicleSeat.cppApp/v8datamodel/VehicleSeat.cpp
VirtualUser.cppApp/v8datamodel/VirtualUser.cpp
Visit.cppApp/v8datamodel/Visit.cpp
Workspace.cppApp/v8datamodel/Workspace.cpp
factoryregistration.cppApp/v8datamodel/factoryregistration.cpp

Function Reference​

1. getBackendAccoutrementState​

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

int getBackendAccoutrementState() const;
PropertyValue
Return Typeint
Modifiersconst
Source LocationApp/include/v8datamodel/Accoutrement.h:148
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getBackendAccoutrementState within App - DataModel & Hierarchy.

  • 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 getBackendAccoutrementState.

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. getAttachmentPoint​

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

CoordinateFrame& getAttachmentPoint() const;
PropertyValue
Return TypeCoordinateFrame&
Modifiersconst const
Source LocationApp/include/v8datamodel/Accoutrement.h:149
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getAttachmentPoint within App - DataModel & Hierarchy.

  • 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 getAttachmentPoint.

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. sleepTimeUp​

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

bool sleepTimeUp() const;
PropertyValue
Return Typebool
Modifiersconst
Source LocationApp/include/v8datamodel/ActionStation.h:24
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes sleepTimeUp within App - DataModel & Hierarchy. Coordinates interactions with return, seconds.

  • 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).
  • Key Internal Calls: return, seconds.

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 sleepTimeUp.

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. debounceTimeUp​

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

bool debounceTimeUp() const;
PropertyValue
Return Typebool
Modifiersconst
Source LocationApp/include/v8datamodel/ActionStation.h:28
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes debounceTimeUp within App - DataModel & Hierarchy. Coordinates interactions with return, seconds.

  • 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).
  • Key Internal Calls: return, seconds.

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 debounceTimeUp.

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. setName​

Status: 🧪 Tested  |  🌐 Cross-Platform Uniform

void setName(const std::string& value);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationApp/include/v8datamodel/ActionStation.h:35
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Instance TODO: Ultra mega super hack - setName is setting the internal Primitive::sizeMultiplier

  • 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: getPartPrimitive, setSizeMultiplier.

How it is Used in Tests​

This function is exercised in 71 test case(s):

  • Instance::WaitForChildReturnsImmediatelyIfChildPresent (App.UnitTest/Instance.cpp:264)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_CHECK_EQUAL(part->getName(), "Renamed")
    • Callsite Snippet: part->setName("PartA");
  • Instance::WaitForSameChildAfterInitialWaitForChild (App.UnitTest/Instance.cpp:289)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_CHECK_EQUAL(part->getName(), "Renamed")
    • Callsite Snippet: part->setName("PartA");
  • Instance::TwoScriptsWaitingForSameChild (App.UnitTest/Instance.cpp:314)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_CHECK(dm->getWorkspace()->findFirstChildByName("Alice") != NULL), BOOST_CHECK(dm->getWorkspace()->findFirstChildByName("Bob") != NULL)
    • Callsite Snippet: part->setName("PartA");
  • Instance::TwoScriptsWaitingForSameChildRenameOnResume (App.UnitTest/Instance.cpp:356)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_CHECK_EQUAL("PartBx", part->getName()), BOOST_CHECK_EQUAL("PartA", part2->getName())
    • Callsite Snippet: part->setName("PartA");

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. ~ActionStation​

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

virtual ~ActionStation();
PropertyValue
Return Typevirtual
ModifiersNone
Source LocationApp/include/v8datamodel/ActionStation.h:47
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Declaration or inline method for ~ActionStation.

  • Control Flow & Execution: Linear execution flow.
  • Memory Management: Standard stack allocation.
  • Concurrency & Thread Safety: Unsynchronized / single-threaded context.
  • Error Handling & Invariants: Standard return value verification.
  • State Mutation: Stateless or local modification.

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 ~ActionStation.

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. getAdornee​

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

PartInstance* getAdornee() const;
PropertyValue
Return TypePartInstance*
Modifiersconst const
Source LocationApp/include/v8datamodel/Adornment.h:18
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getAdornee within App - DataModel & Hierarchy. Coordinates interactions with lock, get.

  • 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).
  • Key Internal Calls: lock, get.

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 getAdornee.

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. getAdornee​

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

PartInstance* getAdornee();
PropertyValue
Return TypePartInstance*
ModifiersNone
Source LocationApp/include/v8datamodel/Adornment.h:20
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getAdornee within App - DataModel & Hierarchy. Coordinates interactions with lock, get.

  • 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: lock, get.

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 getAdornee.

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. getAdorneeDangerous​

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

PartInstance* getAdorneeDangerous() const;
PropertyValue
Return TypePartInstance*
Modifiersconst
Source LocationApp/include/v8datamodel/Adornment.h:22
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getAdorneeDangerous within App - DataModel & Hierarchy. Coordinates interactions with lock, get.

  • 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).
  • Key Internal Calls: lock, get.

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 getAdorneeDangerous.

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. getAdornee​

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

PVInstance* getAdornee() const;
PropertyValue
Return TypePVInstance*
Modifiersconst const
Source LocationApp/include/v8datamodel/Adornment.h:35
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getAdornee within App - DataModel & Hierarchy. Coordinates interactions with lock, get.

  • 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).
  • Key Internal Calls: lock, get.

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 getAdornee.

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. getAdornee​

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

PVInstance* getAdornee();
PropertyValue
Return TypePVInstance*
ModifiersNone
Source LocationApp/include/v8datamodel/Adornment.h:37
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getAdornee within App - DataModel & Hierarchy. Coordinates interactions with lock, get.

  • 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: lock, get.

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 getAdornee.

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. getAdorneeDangerous​

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

PVInstance* getAdorneeDangerous() const;
PropertyValue
Return TypePVInstance*
Modifiersconst
Source LocationApp/include/v8datamodel/Adornment.h:39
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getAdorneeDangerous within App - DataModel & Hierarchy. Coordinates interactions with lock, get.

  • 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).
  • Key Internal Calls: lock, get.

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 getAdorneeDangerous.

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. getPart​

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

PartInstance* getPart() const;
PropertyValue
Return TypePartInstance*
Modifiersconst
Source LocationApp/include/v8datamodel/AnimatableRootJoint.h:14
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getPart within App - DataModel & Hierarchy. Coordinates interactions with get.

  • 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).
  • Key Internal Calls: get.

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 getPart.

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. getAssetId​

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

AnimationId getAssetId() const;
PropertyValue
Return TypeAnimationId
Modifiersconst
Source LocationApp/include/v8datamodel/Animation.h:22
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getAssetId within App - DataModel & Hierarchy.

  • 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 getAssetId.

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. getKeyframeSequence​

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

KeyframeSequence* getKeyframeSequence() const;
PropertyValue
Return TypeKeyframeSequence*
Modifiersconst const
Source LocationApp/include/v8datamodel/AnimationTrackState.h:71
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getKeyframeSequence within App - DataModel & Hierarchy. Coordinates interactions with get.

  • 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).
  • Key Internal Calls: get.

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 getKeyframeSequence.

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. getSpeed​

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

double getSpeed();
PropertyValue
Return Typedouble
ModifiersNone
Source LocationApp/include/v8datamodel/AnimationTrackState.h:78
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getSpeed within App - DataModel & Hierarchy.

  • 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 getSpeed.

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. getIsPlaying​

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

bool getIsPlaying() const;
PropertyValue
Return Typebool
Modifiersconst
Source LocationApp/include/v8datamodel/AnimationTrackState.h:83
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getIsPlaying within App - DataModel & Hierarchy.

  • 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 getIsPlaying.

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. getAnimationTrack​

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

shared_ptr<AnimationTrack> getAnimationTrack() const;
PropertyValue
Return Typeshared_ptr&lt;AnimationTrack&gt;
Modifiersconst
Source LocationApp/include/v8datamodel/AnimationTrackState.h:95
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getAnimationTrack within App - DataModel & Hierarchy.

  • 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 getAnimationTrack.

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. getActiveAnimation​

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

std::string getActiveAnimation() const;
PropertyValue
Return Typestd::string
Modifiersconst
Source LocationApp/include/v8datamodel/Animator.h:85
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getActiveAnimation within App - DataModel & Hierarchy.

  • 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 getActiveAnimation.

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. getAxes​

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

Axes getAxes() const;
PropertyValue
Return TypeAxes
Modifiersconst
Source LocationApp/include/v8datamodel/ArcHandles.h:36
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getAxes within App - DataModel & Hierarchy.

  • 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 getAxes.

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. getVisible​

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

bool getVisible(void) const;
PropertyValue
Return Typebool
Modifiersconst
Source LocationApp/include/v8datamodel/Attachment.h:52
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

For UI, scripting and streaming

  • 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 getVisible.

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. getLocked​

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

bool getLocked(void) const;
PropertyValue
Return Typebool
Modifiersconst
Source LocationApp/include/v8datamodel/Attachment.h:54
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getLocked within App - DataModel & Hierarchy.

  • 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 getLocked.

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. validateFormFactor​

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

void validateFormFactor(FormFactor& value);
PropertyValue
Return Typevoid
Modifiersvirtual
Source LocationApp/include/v8datamodel/BasicPartInstance.h:27
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Declaration or inline method for validateFormFactor.

  • Control Flow & Execution: Linear execution flow.
  • Memory Management: Standard stack allocation.
  • Concurrency & Thread Safety: Unsynchronized / single-threaded context.
  • Error Handling & Invariants: Standard return value verification.
  • State Mutation: Stateless or local modification.

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 validateFormFactor.

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. getLegacyPartType​

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

LegacyPartType getLegacyPartType() const;
PropertyValue
Return TypeLegacyPartType
Modifiersconst
Source LocationApp/include/v8datamodel/BasicPartInstance.h:53
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

override*/ virtual PartType getPartType() const;

  • 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 getLegacyPartType.

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. getAdornee​

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

Instance* getAdornee() const;
PropertyValue
Return TypeInstance*
Modifiersconst const
Source LocationApp/include/v8datamodel/BillboardGui.h:33
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

override*/ bool processMeAndDescendants() const {return false;}

  • 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).
  • Key Internal Calls: lock, get.

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 getAdornee.

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. getAdornee​

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

Instance* getAdornee();
PropertyValue
Return TypeInstance*
ModifiersNone
Source LocationApp/include/v8datamodel/BillboardGui.h:35
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getAdornee within App - DataModel & Hierarchy. Coordinates interactions with lock, get.

  • 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: lock, get.

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 getAdornee.

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. getAdorneeDangerous​

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

Instance* getAdorneeDangerous() const;
PropertyValue
Return TypeInstance*
Modifiersconst
Source LocationApp/include/v8datamodel/BillboardGui.h:37
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getAdorneeDangerous within App - DataModel & Hierarchy. Coordinates interactions with lock, get.

  • 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).
  • Key Internal Calls: lock, get.

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 getAdorneeDangerous.

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. getActive​

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

bool getActive() const;
PropertyValue
Return Typebool
Modifiersconst
Source LocationApp/include/v8datamodel/BillboardGui.h:53
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getActive within App - DataModel & Hierarchy.

  • 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 getActive.

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. getEnabled​

Status: 🧪 Tested  |  🌐 Cross-Platform Uniform

bool getEnabled() const;
PropertyValue
Return Typebool
Modifiersconst
Source LocationApp/include/v8datamodel/BillboardGui.h:56
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getEnabled within App - DataModel & Hierarchy.

  • 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​

This function is exercised in 2 test case(s):

  • PostEffectTest::BlurEffectDefaults (App.UnitTest/PostEffectTest.cpp:13)
    • Usage Pattern: Direct Assertion
    • Assertions Checked: BOOST_CHECK(effect-&gt;getEnabled())
    • Callsite Snippet: BOOST_CHECK(effect-&gt;getEnabled());
  • SoundEffectTests::DistortionPropertiesAndParenting (App.UnitTest/SoundEffectTest.cpp:15)
    • Usage Pattern: Direct Assertion
    • Assertions Checked: BOOST_CHECK(effect-&gt;getEnabled())
    • Callsite Snippet: BOOST_CHECK(effect-&gt;getEnabled());

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. getPlayerToHideFrom​

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

Instance* getPlayerToHideFrom() const;
PropertyValue
Return TypeInstance*
Modifiersconst
Source LocationApp/include/v8datamodel/BillboardGui.h:61
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getPlayerToHideFrom within App - DataModel & Hierarchy. Coordinates interactions with lock, get.

  • 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).
  • Key Internal Calls: lock, get.

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 getPlayerToHideFrom.

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. BlockMesh​

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

public: BlockMesh();
PropertyValue
Return Typepublic:
ModifiersNone
Source LocationApp/include/v8datamodel/BlockMesh.h:12
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Declaration or inline method for BlockMesh.

  • Control Flow & Execution: Linear execution flow.
  • Memory Management: Standard stack allocation.
  • Concurrency & Thread Safety: Unsynchronized / single-threaded context.
  • Error Handling & Invariants: Standard return value verification.
  • State Mutation: Stateless or local modification.

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 BlockMesh.

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. getVertices​

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

std::vector<CSGVertex>& getVertices() const;
PropertyValue
Return Typestd::vector&lt;CSGVertex&gt;&
Modifiersconst const
Source LocationApp/include/v8datamodel/CSGMesh.h:58
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getVertices within App - DataModel & Hierarchy.

  • 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 getVertices.

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. getIndices​

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

std::vector<unsigned int>& getIndices() const;
PropertyValue
Return Typestd::vector&lt;unsigned int&gt;&
Modifiersconst const
Source LocationApp/include/v8datamodel/CSGMesh.h:60
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getIndices within App - DataModel & Hierarchy.

  • 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 getIndices.

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. getIndexRemap​

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

std::vector<unsigned>& getIndexRemap(unsigned idx) const;
PropertyValue
Return Typestd::vector&lt;unsigned&gt;&
Modifiersconst const
Source LocationApp/include/v8datamodel/CSGMesh.h:61
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getIndexRemap within App - DataModel & Hierarchy. Coordinates interactions with RBXASSERT.

  • 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: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).
  • Key Internal Calls: RBXASSERT.

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 getIndexRemap.

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. getVertexRemap​

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

std::vector<unsigned>& getVertexRemap(unsigned idx) const;
PropertyValue
Return Typestd::vector&lt;unsigned&gt;&
Modifiersconst const
Source LocationApp/include/v8datamodel/CSGMesh.h:63
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getVertexRemap within App - DataModel & Hierarchy. Coordinates interactions with RBXASSERT.

  • 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: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).
  • Key Internal Calls: RBXASSERT.

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 getVertexRemap.

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. isBadMesh​

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

bool isBadMesh() const;
PropertyValue
Return Typebool
Modifiersconst
Source LocationApp/include/v8datamodel/CSGMesh.h:66
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes isBadMesh within App - DataModel & Hierarchy.

  • 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 isBadMesh.

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. isValid​

Status: 🧪 Tested  |  🌐 Cross-Platform Uniform

bool isValid() const;
PropertyValue
Return Typebool
Modifiersvirtual const
Source LocationApp/include/v8datamodel/CSGMesh.h:68
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes isValid within App - DataModel & Hierarchy.

  • 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​

This function is exercised in 3 test case(s):

  • URLParser::Split (App.UnitTest/URLParserTest.cpp:7)
    • Usage Pattern: Direct Assertion
    • Assertions Checked: BOOST_CHECK(url.isValid())
    • Callsite Snippet: BOOST_CHECK(url.isValid());
  • URLParser::Normalization (App.UnitTest/URLParserTest.cpp:76)
    • Usage Pattern: Direct Assertion
    • Assertions Checked: BOOST_CHECK(url.isValid())
    • Callsite Snippet: BOOST_CHECK(url.isValid());
  • URLParser::Invalid (App.UnitTest/URLParserTest.cpp:128)
    • Usage Pattern: Direct Assertion
    • Assertions Checked: BOOST_CHECK(!url.isValid()), BOOST_CHECK(!url.isValid()), BOOST_CHECK(!url.isValid())
    • Callsite Snippet: BOOST_CHECK(!url.isValid());

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. translate​

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

void translate(const G3D::Vector3& translation);
PropertyValue
Return Typevoid
Modifiersvirtual
Source LocationApp/include/v8datamodel/CSGMesh.h:72
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Declaration or inline method for translate.

  • Control Flow & Execution: Linear execution flow.
  • Memory Management: Standard stack allocation.
  • Concurrency & Thread Safety: Unsynchronized / single-threaded context.
  • Error Handling & Invariants: Standard return value verification.
  • State Mutation: Stateless or local modification.

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 translate.

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. applyCoordinateFrame​

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

void applyCoordinateFrame(G3D::CoordinateFrame cFrame);
PropertyValue
Return Typevoid
Modifiersvirtual
Source LocationApp/include/v8datamodel/CSGMesh.h:74
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Declaration or inline method for applyCoordinateFrame.

  • Control Flow & Execution: Linear execution flow.
  • Memory Management: Standard stack allocation.
  • Concurrency & Thread Safety: Unsynchronized / single-threaded context.
  • Error Handling & Invariants: Standard return value verification.
  • State Mutation: Stateless or local modification.

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 applyCoordinateFrame.

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. applyTranslation​

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

void applyTranslation(const G3D::Vector3& trans);
PropertyValue
Return Typevoid
Modifiersvirtual
Source LocationApp/include/v8datamodel/CSGMesh.h:76
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Declaration or inline method for applyTranslation.

  • Control Flow & Execution: Linear execution flow.
  • Memory Management: Standard stack allocation.
  • Concurrency & Thread Safety: Unsynchronized / single-threaded context.
  • Error Handling & Invariants: Standard return value verification.
  • State Mutation: Stateless or local modification.

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 applyTranslation.

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. applyColor​

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

void applyColor(const G3D::Vector3& color);
PropertyValue
Return Typevoid
Modifiersvirtual
Source LocationApp/include/v8datamodel/CSGMesh.h:77
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Declaration or inline method for applyColor.

  • Control Flow & Execution: Linear execution flow.
  • Memory Management: Standard stack allocation.
  • Concurrency & Thread Safety: Unsynchronized / single-threaded context.
  • Error Handling & Invariants: Standard return value verification.
  • State Mutation: Stateless or local modification.

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 applyColor.

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. applyScale​

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

void applyScale(const G3D::Vector3& size);
PropertyValue
Return Typevoid
Modifiersvirtual
Source LocationApp/include/v8datamodel/CSGMesh.h:78
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Declaration or inline method for applyScale.

  • Control Flow & Execution: Linear execution flow.
  • Memory Management: Standard stack allocation.
  • Concurrency & Thread Safety: Unsynchronized / single-threaded context.
  • Error Handling & Invariants: Standard return value verification.
  • State Mutation: Stateless or local modification.

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 applyScale.

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. triangulate​

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

void triangulate();
PropertyValue
Return Typevoid
Modifiersvirtual
Source LocationApp/include/v8datamodel/CSGMesh.h:79
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Declaration or inline method for triangulate.

  • Control Flow & Execution: Linear execution flow.
  • Memory Management: Standard stack allocation.
  • Concurrency & Thread Safety: Unsynchronized / single-threaded context.
  • Error Handling & Invariants: Standard return value verification.
  • State Mutation: Stateless or local modification.

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 triangulate.

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. newTriangulate​

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

bool newTriangulate();
PropertyValue
Return Typebool
Modifiersvirtual
Source LocationApp/include/v8datamodel/CSGMesh.h:80
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes newTriangulate within App - DataModel & Hierarchy.

  • 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 newTriangulate.

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. weldMesh​

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

void weldMesh(bool positionOnly = false);
PropertyValue
Return Typevoid
Modifiersvirtual
Source LocationApp/include/v8datamodel/CSGMesh.h:81
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Declaration or inline method for weldMesh.

  • Control Flow & Execution: Linear execution flow.
  • Memory Management: Standard stack allocation.
  • Concurrency & Thread Safety: Unsynchronized / single-threaded context.
  • Error Handling & Invariants: Standard return value verification.
  • State Mutation: Stateless or local modification.

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 weldMesh.

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. buildBRep​

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

void buildBRep();
PropertyValue
Return Typevoid
Modifiersvirtual
Source LocationApp/include/v8datamodel/CSGMesh.h:82
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Declaration or inline method for buildBRep.

  • Control Flow & Execution: Linear execution flow.
  • Memory Management: Standard stack allocation.
  • Concurrency & Thread Safety: Unsynchronized / single-threaded context.
  • Error Handling & Invariants: Standard return value verification.
  • State Mutation: Stateless or local modification.

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 buildBRep.

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. unionMesh​

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

bool unionMesh(const CSGMesh* a, const CSGMesh* b);
PropertyValue
Return Typebool
Modifiersvirtual
Source LocationApp/include/v8datamodel/CSGMesh.h:84
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes unionMesh within App - DataModel & Hierarchy.

  • 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 unionMesh.

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. intersectMesh​

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

bool intersectMesh(const CSGMesh* a, const CSGMesh* b);
PropertyValue
Return Typebool
Modifiersvirtual
Source LocationApp/include/v8datamodel/CSGMesh.h:86
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes intersectMesh within App - DataModel & Hierarchy.

  • 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 intersectMesh.

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. subractMesh​

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

bool subractMesh(const CSGMesh* a, const CSGMesh* b);
PropertyValue
Return Typebool
Modifiersvirtual
Source LocationApp/include/v8datamodel/CSGMesh.h:87
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes subractMesh within App - DataModel & Hierarchy.

  • 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 subractMesh.

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. getBRepBinaryString​

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

std::string getBRepBinaryString() const;
PropertyValue
Return Typestd::string
Modifiersvirtual const
Source LocationApp/include/v8datamodel/CSGMesh.h:94
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes getBRepBinaryString within App - DataModel & Hierarchy.

  • 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 getBRepBinaryString.

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. setBRepFromBinaryString​

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

void setBRepFromBinaryString(const std::string& str);
PropertyValue
Return Typevoid
Modifiersvirtual
Source LocationApp/include/v8datamodel/CSGMesh.h:95
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Declaration or inline method for setBRepFromBinaryString.

  • Control Flow & Execution: Linear execution flow.
  • Memory Management: Standard stack allocation.
  • Concurrency & Thread Safety: Unsynchronized / single-threaded context.
  • Error Handling & Invariants: Standard return value verification.
  • State Mutation: Stateless or local modification.

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 setBRepFromBinaryString.

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. clusterVertices​

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

size_t clusterVertices(float resolution);
PropertyValue
Return Typesize_t
Modifiersvirtual
Source LocationApp/include/v8datamodel/CSGMesh.h:96
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes clusterVertices within App - DataModel & Hierarchy.

  • 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 clusterVertices.

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. makeHalfEdges​

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

bool makeHalfEdges(std::vector< int>& vertexEdges);
PropertyValue
Return Typebool
Modifiersvirtual
Source LocationApp/include/v8datamodel/CSGMesh.h:98
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes makeHalfEdges within App - DataModel & Hierarchy.

  • 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 makeHalfEdges.

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. extentsCenter​

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

G3D::Vector3 extentsCenter();
PropertyValue
Return TypeG3D::Vector3
Modifiersvirtual
Source LocationApp/include/v8datamodel/CSGMesh.h:99
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes extentsCenter within App - DataModel & Hierarchy.

  • 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.
  • 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 extentsCenter.

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. extentsSize​

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

G3D::Vector3 extentsSize();
PropertyValue
Return TypeG3D::Vector3
Modifiersvirtual
Source LocationApp/include/v8datamodel/CSGMesh.h:101
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes extentsSize within App - DataModel & Hierarchy.

  • 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.
  • 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 extentsSize.

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. isRequestQueueEmpty​

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

bool isRequestQueueEmpty();
PropertyValue
Return Typebool
ModifiersNone
Source LocationApp/include/v8datamodel/CacheableContentProvider.h:56
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes isRequestQueueEmpty within App - DataModel & Hierarchy.

  • 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 isRequestQueueEmpty.

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. distanceDefault​

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

float distanceDefault();
PropertyValue
Return Typefloat
Modifiersstatic
Source LocationApp/include/v8datamodel/Camera.h:52
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes distanceDefault within App - DataModel & Hierarchy.

  • 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 distanceDefault.

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. distanceMin​

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

float distanceMin();
PropertyValue
Return Typefloat
Modifiersstatic
Source LocationApp/include/v8datamodel/Camera.h:55
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes distanceMin within App - DataModel & Hierarchy.

  • 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 distanceMin.

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. distanceMax​

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

float distanceMax();
PropertyValue
Return Typefloat
Modifiersstatic
Source LocationApp/include/v8datamodel/Camera.h:56
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes distanceMax within App - DataModel & Hierarchy.

  • 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 distanceMax.

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. distanceMaxCharacter​

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

float distanceMaxCharacter();
PropertyValue
Return Typefloat
Modifiersstatic
Source LocationApp/include/v8datamodel/Camera.h:57
SubsystemApp - DataModel & Hierarchy

How it Works Internally​

Executes distanceMaxCharacter within App - DataModel & Hierarchy.

  • 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 distanceMaxCharacter.

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 4623 additional internal and inline functions in this subsystem. All functions are indexed and cross-referenced in the Complete Function Catalog.