Class globals emexec EmesaryExecutive

the main exeuctive class.
There will be one of these as emexec.ExceModule however multiple instances could be 
created - but only by those who understand scheduling - because it is not necessary
to have more than one - unless we mange to enable some sort of per core threading.

monitor_properties

request monitoring of a list of hash value pairs.

new

register

ident: String (e.g F-15 HUD) inputs: hash of properties to monitor : e.g { AirspeedIndicatorIndicatedMach : "instrumentation/airspeed-indicator/indicated-mach", Alpha : "orientation/alpha-indicated-deg", } : object - must have an update(notification) method that will receive a frame notification : rate is the frame skip update rate (1/update rate). 0 or 1 means full rate : offset is the offset to permit interleave - e.g for two objects to interleave we could have a rate of two and an offset of 0 and 1 which would result in one object being processed per frame

start

stop

timerCallback