VLTrackingIssues stores the issues arrising during startup More information on possible codes: Initialization Issues Such an object is usually passed, when subscribing to the OnTrackerInitializedWithIssues event.
More...
|
|
| VLTrackingIssues (VLIssues vlIssues) |
| |
| string | getInfoForCode (int code) |
| | Checks if the issues contain some code and returns the associated info string. More...
|
| |
| bool | hasCode (int code) |
| | Checks if the issues contain some code. More...
|
| |
|
| VLTrackingIssue [] | issues |
| | Array with the tracking state of all tracking objects. More...
|
| |
| string | message |
| | String message describing the global reason. Have a look into the issues array in order to get a machine readable impression of what was going wrong or what happened. More...
|
| |
VLTrackingIssues stores the issues arrising during startup More information on possible codes: Initialization Issues Such an object is usually passed, when subscribing to the OnTrackerInitializedWithIssues event.
◆ getInfoForCode()
| string VLTrackingIssues.getInfoForCode |
( |
int |
code | ) |
|
|
inline |
Checks if the issues contain some code and returns the associated info string.
- Returns
string, if code was found, "" if no code has been found.
- Parameters
-
◆ hasCode()
| bool VLTrackingIssues.hasCode |
( |
int |
code | ) |
|
|
inline |
Checks if the issues contain some code.
- Returns
true, if code was found, false false.
- Parameters
-
◆ issues
Array with the tracking state of all tracking objects.
◆ message
| string VLTrackingIssues.message |
String message describing the global reason. Have a look into the issues array in order to get a machine readable impression of what was going wrong or what happened.