MHEG  17.9.0
 All Data Structures Files Functions Variables Typedefs Enumerations Macros Pages
inc Directory Reference

Files

file  mh5access.h [code]
 Functions relating to HTTPS Server Access.
 
file  mh5actiontokens.h [code]
 action to string conversion
 
file  mh5base.h [code]
 Basis MHEG5 data types.
 
file  mh5control.h [code]
 Implement MHEG5 engine control functions (i.e. start/stop etc)
 
file  mh5cookies.h [code]
 Functions relating to HTTP Cookie Store.
 
file  mh5date.h [code]
 Date functions.
 
file  mh5debug.h [code]
 Mheg5 logging and debug printing.
 
file  mh5dispBttnRT.h [code]
 
file  mh5display.h [code]
 Implement generic MHEG5-display functions - independent from the OSD These are generic functions used by the MHEG5 engine to manage it's display. These functions are the direct API between the |OSD| and the MHEG5-classes.
 
file  mh5drawtext.h [code]
 MHEG class interface to graphics text render.
 
file  mh5eventtokens.h [code]
 Event to String conversion.
 
file  mh5filegroup.h [code]
 File acceleration for Australia and Souh Africa.
 
file  mh5fileorm.h [code]
 File interface functions to DSMCC component.
 
file  mh5fsnvm.h [code]
 Freesat NVM.
 
file  mh5gate.h [code]
 Implement Functions to support Service Gateways. Functions for standarizing several GroupIDs like +DSM:// +~/ +DSM:/ +CI:/ +etc.
 
file  mh5hash.h [code]
 Functions relating to HTTPS Content Verification.
 
file  mh5hfs.h [code]
 Functions relating to Hybrid file system.
 
file  mh5json.h [code]
 string parsing utility functions described by the [JSON] schema
 
file  mh5keypress.h [code]
 Key Press related functionality.
 
file  mh5misc.h [code]
 Miscellaneous.
 
file  mh5nvm.h [code]
 Persistent storage module. The engine provides a persistent storage for 1024 bytes of data. Data is lost when receiver is is in stand-by or off. The file name used to access this storage is of the form "ram://<name>". It is the responsibility of the DVB to arrange a practice for the use of <name>, such that there are no accidental collisions of file names. When writing a file to persistent storage the receiver executes the following steps:
 
file  mh5object.h [code]
 Implement functions to retrieve MHEG5objects by GroupID and ID.
 
file  mh5parse.h [code]
 string parsing utility functions for MHEG5
 
file  mh5prgs.h [code]
 Implementation of the resident programs which are defined by the current profile.
 
file  mh5profile.h [code]
 This file defines the profile for the MHEG engine.
 
file  mh5queue.h [code]
 Event handling. Implementation of a combined queue for events and actions. This is the eventsystem which drives the MHEG engine.
 
file  mh5sig.h [code]
 Functions relating to HTTPS Signature Certificates.
 
file  mh5storage.h [code]
 Persistent storage module. The engine provides a persistent storage for 1024 bytes of data. Data is lost when receiver is is in stand-by or off. The file name used to access this storage is of the form "ram://<name>". It is the responsibility of the DVB to arrange a practice for the use of <name>, such that there are no accidental collisions of file names. When writing a file to persistent storage the receiver executes the following steps:
 
file  mh5streamevent.h [code]
 Stream event subscription management.
 
file  mh5support.h [code]
 Engine support utility functions for MHEG5.
 
file  mh5tls.h [code]
 Functions relating to TLS certificate store.
 
file  mh5tps.h [code]
 True Persistent Storage functions.
 
file  osdtypes.h [code]
 Define OSD types.
 
file  tmcolor.h [code]
 Definition of colour type for MHEG5 - settings and conversions.
 
file  tmcursor.h [code]
 tmcursor