Background

Currently (Chocolate Doom 3.1.0), both the Mouse Button Presses and Movement is covered with the same Mouse-Event:

d_event.h:

    // Mouse movement event.
    //    data1: Bitfield of buttons currently held down.
    //           (bit 0 = left; bit 1 = right; bit 2 = middle).
    //    data2: X axis mouse movement (turn).
    //    data3: Y axis mouse movement (forward/backward).
    ev_mouse,

That means, with each mouse movement event, also the key button states are updated (again).

Suggestion

Coming from this issue in Crispy, I would like to bring forward the suggestion to separate the two events. This would make additional button-state logic to avoid unintented button re-triggers superfluous for those mouse-buttons, that are not designed to be hold keys.

Since Chocolate Doom is not directly affected by the issue with the currently offered mouse-bindings, I would be prepared to work on such a proposal. Please let me know if such a change in general would be acceptable or not.

Thanks!