On Wed, Sep 07, 2016 at 12:12:43AM +0200, Ulf Brosziewski wrote:
> Hi, I was a bit hasty, I should have mentioned that calling
> wsmouse_input_sync is required here. The equivalent of your
> code would would be this:
>
> if (x != 0 || y != 0 || buttons != ms->sc_buttons) {
> wsmouse_position(ms->sc_wsmousedev, x, y);
> /* ignore proximity, it will cause invalid button 2 events */
> if ((data[0] & 0xf0) != 0xc0)
> wsmouse_buttons(ms->sc_wsmousedev, buttons);
> wsmouse_input_sync();
> }
>
> The WSMOUSE_INPUT macro - a substitute for the old wsmouse_input
> function - does include that call (see wsmousevar.h).
>
> There is a set of functions for reporting input states:
> wsmouse_buttons, wsmouse_motion, wsmouse_position, wsmouse_touch,
> and wsmouse_mtstate (and the somewhat special wsmouse_set and
> wsmouse_mtframe). A driver can call them in any order, and it
> doesn't need to check whether there are deltas, wsmouse does
> this anyway. However, a frame must be finished by a call to
> wsmouse_input_sync. It is this function that generates the
> wscons events.
>
> The new interface has been introduced in 6.0.
>
That explains, thanks you very much for the detailed reply. My sources
were less than a week old, so it will probably just work with the sync
call.
I'll probably send an updated diff when I've fixed the scaling issue.
Frank
