Handling of concurrent mouse button presses isn't xterm-compatible

[GoogleCodeExporter]

In mouse reporting mode, if a mouse button is pressed while another one is
down already, mintty will send a button release code before sending the
button press code for the new button. This is on the grounds that there are
no button-specific release codes, so once two buttons are down, apps can't
tell which one has been released when a release code arrives.

Xterm, however, doesn't worry about that, and simply sends the non-specific
release code whenever any button is released. So mintty should stick with
that behaviour.

Original issue reported on code.google.com by andy.koppe on 14 Oct 2009 at 7:21

[GoogleCodeExporter]

Fixed in r1007 on trunk.

Original comment by andy.koppe on 5 Sep 2010 at 5:24

• Changed state: Fixed
• Added labels: Difficulty-Easy, Milestone-0.9

[GoogleCodeExporter]

Original comment by andy.koppe on 3 Oct 2010 at 3:48

• Changed state: Verified