smarthomatic

User Tools

Site Tools

Trace:
message_definitions_usage

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Last revisionBoth sides next revision
message_definitions_usage [2014/01/01 12:36] – [Read header extension] breaker27message_definitions_usage [2014/01/01 12:37] – [2) Use a specific function for your message type] breaker27
Line 115: Line 115:
 ==== 2) Use a specific function for your message type ==== ==== 2) Use a specific function for your message type ====
  
-As an alternative, you can directly use the function of the appropriate message type like this:+As an alternative, or if the value is only in one of the header extensions, you can directly use the function of the appropriate message type like this:
  
 ''uint32_t messagegroupid = pkg_headerext_**get**_get_messagegroupid();\\ ''uint32_t messagegroupid = pkg_headerext_**get**_get_messagegroupid();\\
Line 121: Line 121:
  
 This is recommended if only requests of one message type are supported in a device. Using the function makes it clear in the source code that e.g. a "Get" packet is assumed to be processed. This is recommended if only requests of one message type are supported in a device. Using the function makes it clear in the source code that e.g. a "Get" packet is assumed to be processed.
- 
 ===== Read message data ===== ===== Read message data =====