MirEvent 2.0

[Daniel van Vugt]

Right, so what you call MirEvent should be MirInputEvent. Because 
MirEvent can include non-input events.

Also, that TouchCount is useful but not enough. If we're to have 
variable-sized MirEvents so as to not waste a whole kilobyte on each 
one, then the generic MirEvent struct needs a generic size (in bytes) 
field. So the code that's passing around (and putting on the wire) 
MirEvents knows how big each one is.


On 21/10/14 13:30, Christopher James Halse Rogers wrote:
> On Tue, Oct 21, 2014 at 1:10 PM, Daniel van Vugt
> <daniel.van.vugt at canonical.com> wrote:
>> Missing (possibly just due to over-simplification in the high level
>> design):
>>
>> * Non-input events
> Correct. Non-input events aren't input events, and so will be treated
> separately :)
>
>
>> * Event struct size field (would allow for compression, omitting
>> unused array entries).
>
> There are no fixed-size arrays there? The only array is the touch array,
> and that already has TouchCount.
>