The future of MirInputEvent

[Robert Carr]

Hi!

I think the value of MirInputEvent is pretty limited. I think it's possible
to defend as correct, for example something may wish to access the time of
events without knowing the event type...even then though this seems pretty
marginal. On the other hand there is no way to implement the conversion we
want without casting inm C so I think we'd probably be better to remove it
in the end...this would also enable us to keep MirEvent as a discriminated
union...where as it stands thats become awkward with MirInputEvent becoming
this like...fake type.

Thanks,
Robert

On Thu, Jun 25, 2015 at 10:00 AM, Alan Griffiths <
alan.griffiths at canonical.com> wrote:

> Hi All,
>
> In case anyone has missed it there's a debate about future direction
> started on two competing MPs:
>
>
>
> https://code.launchpad.net/~alan-griffiths/mir/event-timestamps/+merge/262879
> <
> https://code.launchpad.net/%7Ealan-griffiths/mir/event-timestamps/+merge/262879
> >
>
> https://code.launchpad.net/~alan-griffiths/mir/event-upcast/+merge/262965
> <
> https://code.launchpad.net/%7Ealan-griffiths/mir/event-upcast/+merge/262965
> >
>
> it boils down  to whether the MirInputEvent abstraction is actually
> useful in addition to MirKeyboardEvent, MirPointerEvent and MirTouchEvent.
>
> Please decide before the weekend.
>
> Alan
>
> --
> Mir-devel mailing list
> Mir-devel at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/mir-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/mir-devel/attachments/20150625/c51ea9e0/attachment.html>