remconcoreapi.h File Reference

The operation-specific data field for operations in the Core API has the following format. For commands, there is 1 byte containing the button action. There is optional further data, depending on the operation itself. For instance, Play carries an extra 4 bytes of 'play speed' information. Hence the operation-specific data for a Play command is 5 bytes long. For responses, there are 4 bytes of 'results' data. This is followed by whatever operation-specific data was attached to the originating command (so that the client can identify if necessary what the response is a response to). Hence the operation-specific data for a Play response is 9 bytes long. A buffer size for Core API operations' operation-specific data.

Length of the results data in bytes.

String of same length as result data.

Offset for operation data for commands

Offset for operation data for responses

Offset of button data from beginning of data section. ie the offset of the data for commands is KRemConCoreApiCommandDataOffset +KRemConCoreApiButtonDataOffset. The offset of the button data for responses is KRemConCoreApiResponseDataOffset+KRemConCoreApiButtonDataOffset.

Length of the button action data in bytes.

Button press refresh interval. If the client wants to emulate a button being held down, they send a press. The client must re-post the press within this time, and continue to re-post at least this frequently, otherwise the bearer may assume that the hold has finished. The client may finish the hold by sending a release.

The UID identifying this outer-layer RemCon interface.