IAttachmentPointManager.CreateAttachmentPoint Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Create and register a new attachment point.
public Microsoft.MixedReality.WorldLocking.Core.IAttachmentPoint CreateAttachmentPoint (UnityEngine.Vector3 frozenPosition, Microsoft.MixedReality.WorldLocking.Core.IAttachmentPoint context, Microsoft.MixedReality.WorldLocking.Core.AdjustLocationDelegate locationHandler, Microsoft.MixedReality.WorldLocking.Core.AdjustStateDelegate stateHandler);abstract member CreateAttachmentPoint : UnityEngine.Vector3 * Microsoft.MixedReality.WorldLocking.Core.IAttachmentPoint * Microsoft.MixedReality.WorldLocking.Core.AdjustLocationDelegate * Microsoft.MixedReality.WorldLocking.Core.AdjustStateDelegate -> Microsoft.MixedReality.WorldLocking.Core.IAttachmentPointPublic Function CreateAttachmentPoint (frozenPosition As Vector3, context As IAttachmentPoint, locationHandler As AdjustLocationDelegate, stateHandler As AdjustStateDelegate) As IAttachmentPointParameters
- frozenPosition
- UnityEngine.Vector3
The position in the frozen space at which to start the attachment point
- context
- IAttachmentPoint
The optional context into which to create the attachment point (may be null)
- locationHandler
- AdjustLocationDelegate
Delegate to handle Frozen World engine system adjustments to position
- stateHandler
- AdjustStateDelegate
Delegate to handle Frozen World engine connectivity changes
Returns
The new attachment point interface.
Remarks
The attachment point itself is a fairly opaque handle. Its effects are propagated to the client via the two handlers associated with it. The context interface is optional. It should be given if the new attachment point is conceptually spawned from an existing attachment point (or its target object). If null, then conceptually the new attachment point was spawned from the current camera. The attachment point itself is a fairly opaque handle. The actual adjustments are made via notifications through the two delegates passed into the creation. The locationHandler is strictly to notify of adjustments when refitting (Merge or Refreeze). The stateHandler notifies whether this attachment point is "connected" with the current fragment. Both handlers are optional and may be null.