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 File | Path |
|---|---|
Accoutrement.h | App/include/v8datamodel/Accoutrement.h |
ActionStation.h | App/include/v8datamodel/ActionStation.h |
Adornment.h | App/include/v8datamodel/Adornment.h |
AnimatableRootJoint.h | App/include/v8datamodel/AnimatableRootJoint.h |
Animation.h | App/include/v8datamodel/Animation.h |
AnimationTrackState.h | App/include/v8datamodel/AnimationTrackState.h |
Animator.h | App/include/v8datamodel/Animator.h |
ArcHandles.h | App/include/v8datamodel/ArcHandles.h |
Attachment.h | App/include/v8datamodel/Attachment.h |
BasicPartInstance.h | App/include/v8datamodel/BasicPartInstance.h |
BillboardGui.h | App/include/v8datamodel/BillboardGui.h |
BlockMesh.h | App/include/v8datamodel/BlockMesh.h |
CSGMesh.h | App/include/v8datamodel/CSGMesh.h |
CacheableContentProvider.h | App/include/v8datamodel/CacheableContentProvider.h |
Camera.h | App/include/v8datamodel/Camera.h |
ChangeHistory.h | App/include/v8datamodel/ChangeHistory.h |
CharacterAppearance.h | App/include/v8datamodel/CharacterAppearance.h |
CharacterMesh.h | App/include/v8datamodel/CharacterMesh.h |
ClickDetector.h | App/include/v8datamodel/ClickDetector.h |
CollectionService.h | App/include/v8datamodel/CollectionService.h |
ColorSequence.h | App/include/v8datamodel/ColorSequence.h |
Commands.h | App/include/v8datamodel/Commands.h |
ContentProvider.h | App/include/v8datamodel/ContentProvider.h |
CustomEvent.h | App/include/v8datamodel/CustomEvent.h |
CustomEventReceiver.h | App/include/v8datamodel/CustomEventReceiver.h |
CustomParticleEmitter.h | App/include/v8datamodel/CustomParticleEmitter.h |
CylinderMesh.h | App/include/v8datamodel/CylinderMesh.h |
DataModel.h | App/include/v8datamodel/DataModel.h |
DataModelMesh.h | App/include/v8datamodel/DataModelMesh.h |
DataStore.h | App/include/v8datamodel/DataStore.h |
DataStoreService.h | App/include/v8datamodel/DataStoreService.h |
DebrisService.h | App/include/v8datamodel/DebrisService.h |
DebugSettings.h | App/include/v8datamodel/DebugSettings.h |
Decal.h | App/include/v8datamodel/Decal.h |
DialogChoice.h | App/include/v8datamodel/DialogChoice.h |
DialogRoot.h | App/include/v8datamodel/DialogRoot.h |
EventReplicator.h | App/include/v8datamodel/EventReplicator.h |
Explosion.h | App/include/v8datamodel/Explosion.h |
ExtrudedPartInstance.h | App/include/v8datamodel/ExtrudedPartInstance.h |
FaceInstance.h | App/include/v8datamodel/FaceInstance.h |
Feature.h | App/include/v8datamodel/Feature.h |
FileMesh.h | App/include/v8datamodel/FileMesh.h |
Filters.h | App/include/v8datamodel/Filters.h |
Fire.h | App/include/v8datamodel/Fire.h |
Flag.h | App/include/v8datamodel/Flag.h |
FlyweightService.h | App/include/v8datamodel/FlyweightService.h |
ForceField.h | App/include/v8datamodel/ForceField.h |
Frame.h | App/include/v8datamodel/Frame.h |
FriendService.h | App/include/v8datamodel/FriendService.h |
Game.h | App/include/v8datamodel/Game.h |
GameBasicSettings.h | App/include/v8datamodel/GameBasicSettings.h |
GameSettings.h | App/include/v8datamodel/GameSettings.h |
GamepadService.h | App/include/v8datamodel/GamepadService.h |
GlobalSettings.h | App/include/v8datamodel/GlobalSettings.h |
GuiBase.h | App/include/v8datamodel/GuiBase.h |
GuiBase2d.h | App/include/v8datamodel/GuiBase2d.h |
GuiBase3d.h | App/include/v8datamodel/GuiBase3d.h |
GuiBuilder.h | App/include/v8datamodel/GuiBuilder.h |
GuiLayerCollector.h | App/include/v8datamodel/GuiLayerCollector.h |
GuiMixin.h | App/include/v8datamodel/GuiMixin.h |
GuiObject.h | App/include/v8datamodel/GuiObject.h |
GuiService.h | App/include/v8datamodel/GuiService.h |
GuiText.h | App/include/v8datamodel/GuiText.h |
Gyro.h | App/include/v8datamodel/Gyro.h |
HackDefines.h | App/include/v8datamodel/HackDefines.h |
HandleAdornment.h | App/include/v8datamodel/HandleAdornment.h |
Handles.h | App/include/v8datamodel/Handles.h |
HandlesBase.h | App/include/v8datamodel/HandlesBase.h |
Hopper.h | App/include/v8datamodel/Hopper.h |
HttpRbxApiJob.h | App/include/v8datamodel/HttpRbxApiJob.h |
HttpRbxApiService.h | App/include/v8datamodel/HttpRbxApiService.h |
IAnimatableJoint.h | App/include/v8datamodel/IAnimatableJoint.h |
ICameraOwner.h | App/include/v8datamodel/ICameraOwner.h |
ICharacterSubject.h | App/include/v8datamodel/ICharacterSubject.h |
IModelModifier.h | App/include/v8datamodel/IModelModifier.h |
ImageButton.h | App/include/v8datamodel/ImageButton.h |
InputObject.h | App/include/v8datamodel/InputObject.h |
InsertService.h | App/include/v8datamodel/InsertService.h |
JointInstance.h | App/include/v8datamodel/JointInstance.h |
Keyframe.h | App/include/v8datamodel/Keyframe.h |
KeyframeSequence.h | App/include/v8datamodel/KeyframeSequence.h |
Light.h | App/include/v8datamodel/Light.h |
Lighting.h | App/include/v8datamodel/Lighting.h |
ManualJointHelper.h | App/include/v8datamodel/ManualJointHelper.h |
MarketplaceService.h | App/include/v8datamodel/MarketplaceService.h |
MegaCluster.h | App/include/v8datamodel/MegaCluster.h |
ModelInstance.h | App/include/v8datamodel/ModelInstance.h |
Mouse.h | App/include/v8datamodel/Mouse.h |
MouseCommand.h | App/include/v8datamodel/MouseCommand.h |
NumberSequence.h | App/include/v8datamodel/NumberSequence.h |
PVInstance.h | App/include/v8datamodel/PVInstance.h |
ParametricPartInstance.h | App/include/v8datamodel/ParametricPartInstance.h |
PartCookie.h | App/include/v8datamodel/PartCookie.h |
PartInstance.h | App/include/v8datamodel/PartInstance.h |
PartOperation.h | App/include/v8datamodel/PartOperation.h |
PartOperationAsset.h | App/include/v8datamodel/PartOperationAsset.h |
PathfindingService.h | App/include/v8datamodel/PathfindingService.h |
PersonalServerService.h | App/include/v8datamodel/PersonalServerService.h |
PhysicsInstructions.h | App/include/v8datamodel/PhysicsInstructions.h |
PhysicsService.h | App/include/v8datamodel/PhysicsService.h |
PhysicsSettings.h | App/include/v8datamodel/PhysicsSettings.h |
Platform.h | App/include/v8datamodel/Platform.h |
PlayerGui.h | App/include/v8datamodel/PlayerGui.h |
PlayerScripts.h | App/include/v8datamodel/PlayerScripts.h |
PluginManager.h | App/include/v8datamodel/PluginManager.h |
Pose.h | App/include/v8datamodel/Pose.h |
PostEffect.h | App/include/v8datamodel/PostEffect.h |
Remote.h | App/include/v8datamodel/Remote.h |
RenderHooksService.h | App/include/v8datamodel/RenderHooksService.h |
ReplicatedFirst.h | App/include/v8datamodel/ReplicatedFirst.h |
RootInstance.h | App/include/v8datamodel/RootInstance.h |
SafeChat.h | App/include/v8datamodel/SafeChat.h |
Scale9Frame.h | App/include/v8datamodel/Scale9Frame.h |
ScreenGui.h | App/include/v8datamodel/ScreenGui.h |
ScriptMouseCommand.h | App/include/v8datamodel/ScriptMouseCommand.h |
ScrollingFrame.h | App/include/v8datamodel/ScrollingFrame.h |
Seat.h | App/include/v8datamodel/Seat.h |
Selection.h | App/include/v8datamodel/Selection.h |
SelectionBox.h | App/include/v8datamodel/SelectionBox.h |
SelectionLasso.h | App/include/v8datamodel/SelectionLasso.h |
SelectionSphere.h | App/include/v8datamodel/SelectionSphere.h |
ServerScriptService.h | App/include/v8datamodel/ServerScriptService.h |
SkateboardController.h | App/include/v8datamodel/SkateboardController.h |
SkateboardPlatform.h | App/include/v8datamodel/SkateboardPlatform.h |
Sky.h | App/include/v8datamodel/Sky.h |
Smoke.h | App/include/v8datamodel/Smoke.h |
Sparkles.h | App/include/v8datamodel/Sparkles.h |
SpawnLocation.h | App/include/v8datamodel/SpawnLocation.h |
SpecialMesh.h | App/include/v8datamodel/SpecialMesh.h |
StarterPlayerService.h | App/include/v8datamodel/StarterPlayerService.h |
Stats.h | App/include/v8datamodel/Stats.h |
StudioTool.h | App/include/v8datamodel/StudioTool.h |
StudioToolMouseCommand.h | App/include/v8datamodel/StudioToolMouseCommand.h |
Surface.h | App/include/v8datamodel/Surface.h |
SurfaceGui.h | App/include/v8datamodel/SurfaceGui.h |
SurfaceSelection.h | App/include/v8datamodel/SurfaceSelection.h |
Teams.h | App/include/v8datamodel/Teams.h |
TeleportCallback.h | App/include/v8datamodel/TeleportCallback.h |
TeleportService.h | App/include/v8datamodel/TeleportService.h |
TerrainRegion.h | App/include/v8datamodel/TerrainRegion.h |
Test.h | App/include/v8datamodel/Test.h |
TextBox.h | App/include/v8datamodel/TextBox.h |
Tool.h | App/include/v8datamodel/Tool.h |
ToolsPart.h | App/include/v8datamodel/ToolsPart.h |
UserController.h | App/include/v8datamodel/UserController.h |
UserInputService.h | App/include/v8datamodel/UserInputService.h |
Value.h | App/include/v8datamodel/Value.h |
VehicleSeat.h | App/include/v8datamodel/VehicleSeat.h |
Visit.h | App/include/v8datamodel/Visit.h |
Workspace.h | App/include/v8datamodel/Workspace.h |
Accoutrement.cpp | App/v8datamodel/Accoutrement.cpp |
AdService.cpp | App/v8datamodel/AdService.cpp |
Adornment.cpp | App/v8datamodel/Adornment.cpp |
AnimatableRootJoint.cpp | App/v8datamodel/AnimatableRootJoint.cpp |
Animation.cpp | App/v8datamodel/Animation.cpp |
AnimationController.cpp | App/v8datamodel/AnimationController.cpp |
AnimationTrack.cpp | App/v8datamodel/AnimationTrack.cpp |
AnimationTrackState.cpp | App/v8datamodel/AnimationTrackState.cpp |
Animator.cpp | App/v8datamodel/Animator.cpp |
ArcHandles.cpp | App/v8datamodel/ArcHandles.cpp |
AssetService.cpp | App/v8datamodel/AssetService.cpp |
Attachment.cpp | App/v8datamodel/Attachment.cpp |
Backpack.cpp | App/v8datamodel/Backpack.cpp |
BadgeService.cpp | App/v8datamodel/BadgeService.cpp |
BaseRenderJob.cpp | App/v8datamodel/BaseRenderJob.cpp |
BasicPartInstance.cpp | App/v8datamodel/BasicPartInstance.cpp |
BevelMesh.cpp | App/v8datamodel/BevelMesh.cpp |
BillboardGui.cpp | App/v8datamodel/BillboardGui.cpp |
Bindable.cpp | App/v8datamodel/Bindable.cpp |
CSGDictionaryService.cpp | App/v8datamodel/CSGDictionaryService.cpp |
CSGMesh.cpp | App/v8datamodel/CSGMesh.cpp |
Camera.cpp | App/v8datamodel/Camera.cpp |
ChangeHistory.cpp | App/v8datamodel/ChangeHistory.cpp |
CharacterAppearance.cpp | App/v8datamodel/CharacterAppearance.cpp |
CharacterMesh.cpp | App/v8datamodel/CharacterMesh.cpp |
ChatService.cpp | App/v8datamodel/ChatService.cpp |
ClickDetector.cpp | App/v8datamodel/ClickDetector.cpp |
CollectionService.cpp | App/v8datamodel/CollectionService.cpp |
ColorSequence.cpp | App/v8datamodel/ColorSequence.cpp |
Commands.cpp | App/v8datamodel/Commands.cpp |
Configuration.cpp | App/v8datamodel/Configuration.cpp |
ContextActionService.cpp | App/v8datamodel/ContextActionService.cpp |
CookiesEngineService.cpp | App/v8datamodel/CookiesEngineService.cpp |
CustomEventReceiver.cpp | App/v8datamodel/CustomEventReceiver.cpp |
CustomParticleEmitter.cpp | App/v8datamodel/CustomParticleEmitter.cpp |
DataModel.cpp | App/v8datamodel/DataModel.cpp |
DataModelJob.cpp | App/v8datamodel/DataModelJob.cpp |
DataModelMesh.cpp | App/v8datamodel/DataModelMesh.cpp |
DataStore.cpp | App/v8datamodel/DataStore.cpp |
DataStoreService.cpp | App/v8datamodel/DataStoreService.cpp |
DebrisService.cpp | App/v8datamodel/DebrisService.cpp |
DebugSettings.cpp | App/v8datamodel/DebugSettings.cpp |
Decal.cpp | App/v8datamodel/Decal.cpp |
DialogChoice.cpp | App/v8datamodel/DialogChoice.cpp |
DialogRoot.cpp | App/v8datamodel/DialogRoot.cpp |
Explosion.cpp | App/v8datamodel/Explosion.cpp |
ExtrudedPartInstance.cpp | App/v8datamodel/ExtrudedPartInstance.cpp |
FaceInstance.cpp | App/v8datamodel/FaceInstance.cpp |
FastLogSettings.cpp | App/v8datamodel/FastLogSettings.cpp |
Feature.cpp | App/v8datamodel/Feature.cpp |
FileMesh.cpp | App/v8datamodel/FileMesh.cpp |
Filters.cpp | App/v8datamodel/Filters.cpp |
Fire.cpp | App/v8datamodel/Fire.cpp |
Flag.cpp | App/v8datamodel/Flag.cpp |
FlagStand.cpp | App/v8datamodel/FlagStand.cpp |
FloorWire.cpp | App/v8datamodel/FloorWire.cpp |
FlyweightService.cpp | App/v8datamodel/FlyweightService.cpp |
Folder.cpp | App/v8datamodel/Folder.cpp |
ForceField.cpp | App/v8datamodel/ForceField.cpp |
Frame.cpp | App/v8datamodel/Frame.cpp |
FriendService.cpp | App/v8datamodel/FriendService.cpp |
Game.cpp | App/v8datamodel/Game.cpp |
GameBasicSettings.cpp | App/v8datamodel/GameBasicSettings.cpp |
GamePassService.cpp | App/v8datamodel/GamePassService.cpp |
GameSettings.cpp | App/v8datamodel/GameSettings.cpp |
GamepadService.cpp | App/v8datamodel/GamepadService.cpp |
GeometryService.cpp | App/v8datamodel/GeometryService.cpp |
GlobalSettings.cpp | App/v8datamodel/GlobalSettings.cpp |
GuiBase.cpp | App/v8datamodel/GuiBase.cpp |
GuiBase2d.cpp | App/v8datamodel/GuiBase2d.cpp |
GuiBase3d.cpp | App/v8datamodel/GuiBase3d.cpp |
GuiBuilder.cpp | App/v8datamodel/GuiBuilder.cpp |
GuiLayerCollector.cpp | App/v8datamodel/GuiLayerCollector.cpp |
GuiObject.cpp | App/v8datamodel/GuiObject.cpp |
GuiService.cpp | App/v8datamodel/GuiService.cpp |
Gyro.cpp | App/v8datamodel/Gyro.cpp |
HandleAdornment.cpp | App/v8datamodel/HandleAdornment.cpp |
Handles.cpp | App/v8datamodel/Handles.cpp |
HandlesBase.cpp | App/v8datamodel/HandlesBase.cpp |
HapticService.cpp | App/v8datamodel/HapticService.cpp |
Hopper.cpp | App/v8datamodel/Hopper.cpp |
HttpRbxApiService.cpp | App/v8datamodel/HttpRbxApiService.cpp |
HttpService.cpp | App/v8datamodel/HttpService.cpp |
ICharacterSubject.cpp | App/v8datamodel/ICharacterSubject.cpp |
IEquipable.cpp | App/v8datamodel/IEquipable.cpp |
ImageButton.cpp | App/v8datamodel/ImageButton.cpp |
ImageLabel.cpp | App/v8datamodel/ImageLabel.cpp |
InputObject.cpp | App/v8datamodel/InputObject.cpp |
InsertService.cpp | App/v8datamodel/InsertService.cpp |
JointInstance.cpp | App/v8datamodel/JointInstance.cpp |
JointsService.cpp | App/v8datamodel/JointsService.cpp |
Keyframe.cpp | App/v8datamodel/Keyframe.cpp |
KeyframeSequence.cpp | App/v8datamodel/KeyframeSequence.cpp |
KeyframeSequenceProvider.cpp | App/v8datamodel/KeyframeSequenceProvider.cpp |
Light.cpp | App/v8datamodel/Light.cpp |
Lighting.cpp | App/v8datamodel/Lighting.cpp |
LogService.cpp | App/v8datamodel/LogService.cpp |
LoginService.cpp | App/v8datamodel/LoginService.cpp |
ManualJointHelper.cpp | App/v8datamodel/ManualJointHelper.cpp |
MarketplaceService.cpp | App/v8datamodel/MarketplaceService.cpp |
MegaCluster.cpp | App/v8datamodel/MegaCluster.cpp |
Message.cpp | App/v8datamodel/Message.cpp |
ModelInstance.cpp | App/v8datamodel/ModelInstance.cpp |
Mouse.cpp | App/v8datamodel/Mouse.cpp |
MouseCommand.cpp | App/v8datamodel/MouseCommand.cpp |
NonReplicatedCSGDictionaryService.cpp | App/v8datamodel/NonReplicatedCSGDictionaryService.cpp |
NotificationService.cpp | App/v8datamodel/NotificationService.cpp |
NumberRange.cpp | App/v8datamodel/NumberRange.cpp |
NumberSequence.cpp | App/v8datamodel/NumberSequence.cpp |
PVInstance.cpp | App/v8datamodel/PVInstance.cpp |
PartCookie.cpp | App/v8datamodel/PartCookie.cpp |
PartInstance.cpp | App/v8datamodel/PartInstance.cpp |
PartOperation.cpp | App/v8datamodel/PartOperation.cpp |
PartOperationAsset.cpp | App/v8datamodel/PartOperationAsset.cpp |
PathfindingService.cpp | App/v8datamodel/PathfindingService.cpp |
PersonalServerService.cpp | App/v8datamodel/PersonalServerService.cpp |
PhysicsInstructions.cpp | App/v8datamodel/PhysicsInstructions.cpp |
PhysicsService.cpp | App/v8datamodel/PhysicsService.cpp |
PhysicsSettings.cpp | App/v8datamodel/PhysicsSettings.cpp |
Platform.cpp | App/v8datamodel/Platform.cpp |
PlatformService.cpp | App/v8datamodel/PlatformService.cpp |
PlayerGui.cpp | App/v8datamodel/PlayerGui.cpp |
PlayerMouse.cpp | App/v8datamodel/PlayerMouse.cpp |
PlayerScripts.cpp | App/v8datamodel/PlayerScripts.cpp |
PluginManager.cpp | App/v8datamodel/PluginManager.cpp |
PluginMouse.cpp | App/v8datamodel/PluginMouse.cpp |
PointsService.cpp | App/v8datamodel/PointsService.cpp |
Pose.cpp | App/v8datamodel/Pose.cpp |
PostEffect.cpp | App/v8datamodel/PostEffect.cpp |
PrismInstance.cpp | App/v8datamodel/PrismInstance.cpp |
PyramidInstance.cpp | App/v8datamodel/PyramidInstance.cpp |
Remote.cpp | App/v8datamodel/Remote.cpp |
RenderHooksService.cpp | App/v8datamodel/RenderHooksService.cpp |
ReplicatedFirst.cpp | App/v8datamodel/ReplicatedFirst.cpp |
RootInstance.cpp | App/v8datamodel/RootInstance.cpp |
SafeChat.cpp | App/v8datamodel/SafeChat.cpp |
Scale9Frame.cpp | App/v8datamodel/Scale9Frame.cpp |
ScreenGui.cpp | App/v8datamodel/ScreenGui.cpp |
ScriptMouseCommand.cpp | App/v8datamodel/ScriptMouseCommand.cpp |
ScrollingFrame.cpp | App/v8datamodel/ScrollingFrame.cpp |
Seat.cpp | App/v8datamodel/Seat.cpp |
Selection.cpp | App/v8datamodel/Selection.cpp |
SelectionBox.cpp | App/v8datamodel/SelectionBox.cpp |
SelectionLasso.cpp | App/v8datamodel/SelectionLasso.cpp |
SelectionSphere.cpp | App/v8datamodel/SelectionSphere.cpp |
ServerScriptService.cpp | App/v8datamodel/ServerScriptService.cpp |
ServerStorage.cpp | App/v8datamodel/ServerStorage.cpp |
SkateboardController.cpp | App/v8datamodel/SkateboardController.cpp |
SkateboardPlatform.cpp | App/v8datamodel/SkateboardPlatform.cpp |
Sky.cpp | App/v8datamodel/Sky.cpp |
SleepingJob.cpp | App/v8datamodel/SleepingJob.cpp |
Smoke.cpp | App/v8datamodel/Smoke.cpp |
SocialService.cpp | App/v8datamodel/SocialService.cpp |
SolidModelContentProvider.cpp | App/v8datamodel/SolidModelContentProvider.cpp |
Sparkles.cpp | App/v8datamodel/Sparkles.cpp |
SpawnLocation.cpp | App/v8datamodel/SpawnLocation.cpp |
SpecialMesh.cpp | App/v8datamodel/SpecialMesh.cpp |
StarterPlayerService.cpp | App/v8datamodel/StarterPlayerService.cpp |
Stats.cpp | App/v8datamodel/Stats.cpp |
StudioTool.cpp | App/v8datamodel/StudioTool.cpp |
StudioToolMouseCommand.cpp | App/v8datamodel/StudioToolMouseCommand.cpp |
StudioToolVerb.cpp | App/v8datamodel/StudioToolVerb.cpp |
Surface.cpp | App/v8datamodel/Surface.cpp |
SurfaceGui.cpp | App/v8datamodel/SurfaceGui.cpp |
SurfaceSelection.cpp | App/v8datamodel/SurfaceSelection.cpp |
Team.cpp | App/v8datamodel/Team.cpp |
Teams.cpp | App/v8datamodel/Teams.cpp |
TeleportService.cpp | App/v8datamodel/TeleportService.cpp |
TerrainRegion.cpp | App/v8datamodel/TerrainRegion.cpp |
Test.cpp | App/v8datamodel/Test.cpp |
TextBox.cpp | App/v8datamodel/TextBox.cpp |
TextButton.cpp | App/v8datamodel/TextButton.cpp |
TextLabel.cpp | App/v8datamodel/TextLabel.cpp |
TextService.cpp | App/v8datamodel/TextService.cpp |
TextureTrail.cpp | App/v8datamodel/TextureTrail.cpp |
TimerService.cpp | App/v8datamodel/TimerService.cpp |
Tool.cpp | App/v8datamodel/Tool.cpp |
ToolMouseCommand.cpp | App/v8datamodel/ToolMouseCommand.cpp |
ToolsModel.cpp | App/v8datamodel/ToolsModel.cpp |
ToolsPart.cpp | App/v8datamodel/ToolsPart.cpp |
ToolsSurface.cpp | App/v8datamodel/ToolsSurface.cpp |
TouchInputService.cpp | App/v8datamodel/TouchInputService.cpp |
TouchTransmitter.cpp | App/v8datamodel/TouchTransmitter.cpp |
TweenService.cpp | App/v8datamodel/TweenService.cpp |
UserController.cpp | App/v8datamodel/UserController.cpp |
UserInputService.cpp | App/v8datamodel/UserInputService.cpp |
Value.cpp | App/v8datamodel/Value.cpp |
VehicleSeat.cpp | App/v8datamodel/VehicleSeat.cpp |
VirtualUser.cpp | App/v8datamodel/VirtualUser.cpp |
Visit.cpp | App/v8datamodel/Visit.cpp |
Workspace.cpp | App/v8datamodel/Workspace.cpp |
factoryregistration.cpp | App/v8datamodel/factoryregistration.cpp |
Function Reference
1. getBackendAccoutrementState
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
int getBackendAccoutrementState() const;
| Property | Value |
|---|---|
| Return Type | int |
| Modifiers | const |
| Source Location | App/include/v8datamodel/Accoutrement.h:148 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | CoordinateFrame& |
| Modifiers | const const |
| Source Location | App/include/v8datamodel/Accoutrement.h:149 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | const |
| Source Location | App/include/v8datamodel/ActionStation.h:24 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | const |
| Source Location | App/include/v8datamodel/ActionStation.h:28 |
| Subsystem | App - 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.
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | App/include/v8datamodel/ActionStation.h:35 |
| Subsystem | App - 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");
- Usage Pattern:
Instance::WaitForSameChildAfterInitialWaitForChild(App.UnitTest/Instance.cpp:289)- Usage Pattern:
Direct Call - Assertions Checked:
BOOST_CHECK_EQUAL(part->getName(), "Renamed") - Callsite Snippet:
part->setName("PartA");
- Usage Pattern:
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");
- Usage Pattern:
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");
- Usage Pattern:
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();
| Property | Value |
|---|---|
| Return Type | virtual |
| Modifiers | None |
| Source Location | App/include/v8datamodel/ActionStation.h:47 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | PartInstance* |
| Modifiers | const const |
| Source Location | App/include/v8datamodel/Adornment.h:18 |
| Subsystem | App - 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.
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();
| Property | Value |
|---|---|
| Return Type | PartInstance* |
| Modifiers | None |
| Source Location | App/include/v8datamodel/Adornment.h:20 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | PartInstance* |
| Modifiers | const |
| Source Location | App/include/v8datamodel/Adornment.h:22 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | PVInstance* |
| Modifiers | const const |
| Source Location | App/include/v8datamodel/Adornment.h:35 |
| Subsystem | App - 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.
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();
| Property | Value |
|---|---|
| Return Type | PVInstance* |
| Modifiers | None |
| Source Location | App/include/v8datamodel/Adornment.h:37 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | PVInstance* |
| Modifiers | const |
| Source Location | App/include/v8datamodel/Adornment.h:39 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | PartInstance* |
| Modifiers | const |
| Source Location | App/include/v8datamodel/AnimatableRootJoint.h:14 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | AnimationId |
| Modifiers | const |
| Source Location | App/include/v8datamodel/Animation.h:22 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | KeyframeSequence* |
| Modifiers | const const |
| Source Location | App/include/v8datamodel/AnimationTrackState.h:71 |
| Subsystem | App - 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.
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();
| Property | Value |
|---|---|
| Return Type | double |
| Modifiers | None |
| Source Location | App/include/v8datamodel/AnimationTrackState.h:78 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | const |
| Source Location | App/include/v8datamodel/AnimationTrackState.h:83 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | shared_ptr<AnimationTrack> |
| Modifiers | const |
| Source Location | App/include/v8datamodel/AnimationTrackState.h:95 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | std::string |
| Modifiers | const |
| Source Location | App/include/v8datamodel/Animator.h:85 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | Axes |
| Modifiers | const |
| Source Location | App/include/v8datamodel/ArcHandles.h:36 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | const |
| Source Location | App/include/v8datamodel/Attachment.h:52 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | const |
| Source Location | App/include/v8datamodel/Attachment.h:54 |
| Subsystem | App - 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.
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/BasicPartInstance.h:27 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | LegacyPartType |
| Modifiers | const |
| Source Location | App/include/v8datamodel/BasicPartInstance.h:53 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | Instance* |
| Modifiers | const const |
| Source Location | App/include/v8datamodel/BillboardGui.h:33 |
| Subsystem | App - 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.
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();
| Property | Value |
|---|---|
| Return Type | Instance* |
| Modifiers | None |
| Source Location | App/include/v8datamodel/BillboardGui.h:35 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | Instance* |
| Modifiers | const |
| Source Location | App/include/v8datamodel/BillboardGui.h:37 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | const |
| Source Location | App/include/v8datamodel/BillboardGui.h:53 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | const |
| Source Location | App/include/v8datamodel/BillboardGui.h:56 |
| Subsystem | App - 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->getEnabled()) - Callsite Snippet:
BOOST_CHECK(effect->getEnabled());
- Usage Pattern:
SoundEffectTests::DistortionPropertiesAndParenting(App.UnitTest/SoundEffectTest.cpp:15)- Usage Pattern:
Direct Assertion - Assertions Checked:
BOOST_CHECK(effect->getEnabled()) - Callsite Snippet:
BOOST_CHECK(effect->getEnabled());
- Usage Pattern:
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;
| Property | Value |
|---|---|
| Return Type | Instance* |
| Modifiers | const |
| Source Location | App/include/v8datamodel/BillboardGui.h:61 |
| Subsystem | App - 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.
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();
| Property | Value |
|---|---|
| Return Type | public: |
| Modifiers | None |
| Source Location | App/include/v8datamodel/BlockMesh.h:12 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | std::vector<CSGVertex>& |
| Modifiers | const const |
| Source Location | App/include/v8datamodel/CSGMesh.h:58 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | std::vector<unsigned int>& |
| Modifiers | const const |
| Source Location | App/include/v8datamodel/CSGMesh.h:60 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | std::vector<unsigned>& |
| Modifiers | const const |
| Source Location | App/include/v8datamodel/CSGMesh.h:61 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | std::vector<unsigned>& |
| Modifiers | const const |
| Source Location | App/include/v8datamodel/CSGMesh.h:63 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | const |
| Source Location | App/include/v8datamodel/CSGMesh.h:66 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | virtual const |
| Source Location | App/include/v8datamodel/CSGMesh.h:68 |
| Subsystem | App - 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());
- Usage Pattern:
URLParser::Normalization(App.UnitTest/URLParserTest.cpp:76)- Usage Pattern:
Direct Assertion - Assertions Checked:
BOOST_CHECK(url.isValid()) - Callsite Snippet:
BOOST_CHECK(url.isValid());
- Usage Pattern:
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());
- Usage Pattern:
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/CSGMesh.h:72 |
| Subsystem | App - 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.
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/CSGMesh.h:74 |
| Subsystem | App - 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.
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/CSGMesh.h:76 |
| Subsystem | App - 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.
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/CSGMesh.h:77 |
| Subsystem | App - 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.
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/CSGMesh.h:78 |
| Subsystem | App - 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.
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();
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/CSGMesh.h:79 |
| Subsystem | App - 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.
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();
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/CSGMesh.h:80 |
| Subsystem | App - 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.
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/CSGMesh.h:81 |
| Subsystem | App - 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.
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();
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/CSGMesh.h:82 |
| Subsystem | App - 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.
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);
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/CSGMesh.h:84 |
| Subsystem | App - 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.
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);
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/CSGMesh.h:86 |
| Subsystem | App - 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.
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);
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/CSGMesh.h:87 |
| Subsystem | App - 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.
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;
| Property | Value |
|---|---|
| Return Type | std::string |
| Modifiers | virtual const |
| Source Location | App/include/v8datamodel/CSGMesh.h:94 |
| Subsystem | App - 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.
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/CSGMesh.h:95 |
| Subsystem | App - 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.
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);
| Property | Value |
|---|---|
| Return Type | size_t |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/CSGMesh.h:96 |
| Subsystem | App - 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.
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);
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/CSGMesh.h:98 |
| Subsystem | App - 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.
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();
| Property | Value |
|---|---|
| Return Type | G3D::Vector3 |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/CSGMesh.h:99 |
| Subsystem | App - 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.
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();
| Property | Value |
|---|---|
| Return Type | G3D::Vector3 |
| Modifiers | virtual |
| Source Location | App/include/v8datamodel/CSGMesh.h:101 |
| Subsystem | App - 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.
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();
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | None |
| Source Location | App/include/v8datamodel/CacheableContentProvider.h:56 |
| Subsystem | App - 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.
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();
| Property | Value |
|---|---|
| Return Type | float |
| Modifiers | static |
| Source Location | App/include/v8datamodel/Camera.h:52 |
| Subsystem | App - 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.
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();
| Property | Value |
|---|---|
| Return Type | float |
| Modifiers | static |
| Source Location | App/include/v8datamodel/Camera.h:55 |
| Subsystem | App - 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.
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();
| Property | Value |
|---|---|
| Return Type | float |
| Modifiers | static |
| Source Location | App/include/v8datamodel/Camera.h:56 |
| Subsystem | App - 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.
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();
| Property | Value |
|---|---|
| Return Type | float |
| Modifiers | static |
| Source Location | App/include/v8datamodel/Camera.h:57 |
| Subsystem | App - 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.
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.
There are 4623 additional internal and inline functions in this subsystem. All functions are indexed and cross-referenced in the Complete Function Catalog.