<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
> From: brummer-@web.de<br><div>> To: d@drobilla.net<br>> CC: nickycopeland@hotmail.com; linux-audio-dev@lists.linuxaudio.org<br>> I think most modern apps use middle mouse button today for midi<br>> connection. Laptops witch didn't have a middle mouse button often even<br>> didn't have a midi in connection so there is nothing to loose. <br>> And, for that case one can provide a midi table to choose connections<br>> from.<br>> <br>> A click to "go here", seems on the other hand like a bad Idea for me.<br><br>So there are a few options for middle mouse:<br><br>a. it does not exist since we have 2 button mouse<br>b. it does, or is emulated and implies 'jump to here'<br>c. it does, or is emulated and implies 'post pop-up to request value'<br>d. it does, or is emulated and implies 'MIDI CC Register'<br><br>That probably needs to be voted on to see what is generally implemented. <br>It might also make sense to post on LAU and see what people generally<br>anticipate, as ever there can be disconnects between users and developers.<br><br>Out of interest, how many apps respect mouse buttons 4 and buttons 5 for <br>scroll up/down? This is the middle-mouse-wheel, it should at least be part of <br>the proposal, then perhaps also with 'Control', and 'Shift'?<br><br>> Most time you have a underling adjustment witch have a much wider range<br>> then the screen counterpart (the controller) represent so that it is<br>> impossible to click on a point and get the wonted value. <br>> <br>> But overall, a agreement about the different use cases of controller<br>> keys will be very fine and useful for the Linux Audio World.<br>> <br>> <br>> <br></div> </div></body>
</html>