• @TomWS, you are absolutely correct w/ the C approach... with JS this is a bit different, because the 'system' (language and implementation) does memory handling for you... In order to do so, it needs information which then leads to memory inefficiency, something you do not like very much when already memory strapped / bound. BUT there are some trickeries used all across, even in the (adafruit graphics) C world: compose 2 16 bits to a 32 bit one (or worse, 2 8 bit to a 16 bit one and then combine it with another 16... etc.. I guess you get this muddying. The array would then include a fixed number of 32 bit entries per event and when processing they have to be taking them apart, with shift and masking (and making the MSBit right to not venture into the issue of packing a positive value and unpacking a negative one and vice versa). More (backwards) advanced things are then to provide some structure information in the first byte to allow variable number of entries in a 'record' stored as 32-bit Uints... ;-) or more :\ - take it for what you look at it...

About

Avatar for allObjects @allObjects started