The VLModelTrackerBehaviour_v1 contains all functions, which are specific for the ModelTracker_v1.
More...
Inherits VLWorkerReferenceBehaviour.
The VLModelTrackerBehaviour_v1 contains all functions, which are specific for the ModelTracker_v1.
◆ GetModelProperties()
bool VLModelTrackerBehaviour_v1.GetModelProperties |
( |
| ) |
|
|
inline |
◆ GetModelPropertiesAction()
delegate void VLModelTrackerBehaviour_v1.GetModelPropertiesAction |
( |
VLModelProperties [] |
properties | ) |
|
◆ HasWorkerReference()
bool VLModelTrackerBehaviour_v1.HasWorkerReference |
( |
| ) |
|
|
inline |
◆ ReadInitData()
void VLModelTrackerBehaviour_v1.ReadInitData |
( |
string |
uri | ) |
|
|
inline |
Loads the captured initialization data as file from a custom location.
In order to load init data at best use a static uri. A common way is for each platform, is using "local_storage_dir" scheme which can be used as file prefix. This scheme points to different locations depending on the platform:
- Windows: Current users home directory
- MacOS: Current users document directory
- iOS / Android: The current applications document directory
- Parameters
-
uri | Will be used as filename and path. A time stamp and the file extension will be appended automatically. A plausible value could be for example "local_storage_dir:MyInitData_". |
◆ ReadInitDataAction()
delegate void VLModelTrackerBehaviour_v1.ReadInitDataAction |
( |
bool |
success | ) |
|
Delegate for ReadInitDataAction events.
- Parameters
-
success | true , on success; false , otherwise. |
◆ RemoveModel()
void VLModelTrackerBehaviour_v1.RemoveModel |
( |
string |
name | ) |
|
|
inline |
◆ ResetInitData()
void VLModelTrackerBehaviour_v1.ResetInitData |
( |
| ) |
|
|
inline |
Reset the offline initialization data.
In order to reset the initialization data loaded at the beginning this fuction can be called. The init data learned on the fly, will still be maintained and can be reset by issuing a hard reset.
◆ ResetInitDataAction()
delegate void VLModelTrackerBehaviour_v1.ResetInitDataAction |
( |
bool |
success | ) |
|
◆ ResetTrackingHard()
void VLModelTrackerBehaviour_v1.ResetTrackingHard |
( |
| ) |
|
|
inline |
Reset the tracking and all keyframes.
◆ ResetTrackingSoft()
void VLModelTrackerBehaviour_v1.ResetTrackingSoft |
( |
| ) |
|
|
inline |
◆ SetModelProperty()
bool VLModelTrackerBehaviour_v1.SetModelProperty |
( |
string |
name, |
|
|
string |
property, |
|
|
bool |
state |
|
) |
| |
|
inline |
◆ SetModelURI()
void VLModelTrackerBehaviour_v1.SetModelURI |
( |
string |
modelURI | ) |
|
|
inline |
Sets the modelURI to a new value and thus loads a new model.
- Parameters
-
modelURI | URI of the model, which should be used for tracking. |
◆ WriteInitData() [1/2]
void VLModelTrackerBehaviour_v1.WriteInitData |
( |
| ) |
|
|
inline |
Write the captured initialization data as file to default location with default name.
A default name will be used for the file ("InitData_timestamp.binz"). The file will be written to different locations depending on the platform:
- Windows: Current users home directory
- MacOS: Current users document directory
- iOS / Android: The current applications document directory
◆ WriteInitData() [2/2]
void VLModelTrackerBehaviour_v1.WriteInitData |
( |
string |
filePrefix | ) |
|
|
inline |
Write the captured initialization data as file to custom location with custom name.
In order to avoid having to use a different file path for each platform, the "local_storage_dir" scheme can be used as file prefix. This scheme points to different locations depending on the platform:
- Windows: Current users home directory
- MacOS: Current users document directory
- iOS / Android: The current applications document directory
- Parameters
-
filePrefix | Will be used as filename and path. A time stamp and the file extension will be appended automatically. A plausible value could be for example "local_storage_dir:MyInitData_". |
◆ WriteInitDataAction()
delegate void VLModelTrackerBehaviour_v1.WriteInitDataAction |
( |
bool |
success | ) |
|
◆ OnSetModelURI
Event which will be emitted before "SetModelURI" has been called.
◆ OnSetModelURIFinished
Event which will be emitted after "SetModelURI" has been finished
◆ OnGetModelProperties
Event which will be emitted when the model properties have been rquested by GetModelStateProperties.
◆ OnReadInitData
Event which will be emitted after a the initialization data has been loaded from an uri.
◆ OnResetInitData
Event which will be emitted after a the initialization data has been reset from an uri.
◆ OnWriteInitData
Event which will be emitted after a the initialization were written to disk.