Member values
| Member name | Data type | Description | Usage |
|---|---|---|---|
| action_event | int | Action event type | You can manipulate the field action_event as if it were a regular field. To clear the value of action_event and reset it to the default value for its type, you call the ClearField() method of the Message interface. |
| handle | ActionHandle | Identifies the action for which this event occured | To set handle, you simply assign a value directly to a field within handle. You can also use the parent message’s HasField() method to check if a message type field value has been set. |
| timestamp | Timestamp | Event timestamp | To set timestamp, you simply assign a value directly to a field within timestamp. You can also use the parent message’s HasField() method to check if a message type field value has been set. |
| user_handle | UserProfileHandle | User that caused the action event | To set user_handle, you simply assign a value directly to a field within user_handle. You can also use the parent message’s HasField() method to check if a message type field value has been set. |
| abort_details | int | Details if action_event is equal to ACTION_ABORT | You can manipulate the field abort_details as if it were a regular field. To clear the value of abort_details and reset it to the default value for its type, you call the ClearField() method of the Message interface. |
| connection | Connection | Connection that caused the action event | To set connection, you simply assign a value directly to a field within connection. You can also use the parent message’s HasField() method to check if a message type field value has been set. |
| trajectory_info | TrajectoryInfo | Additional information from the current action | Repeated message fields are represented as an object that acts like a Python sequence. However, You must use add() instead of append(). It also has an extend() function that appends an entire list of messages, but makes a copy of every message in the list. |
Parent topic: Base (Python)