<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: d@drobilla.net<br><div>> Just a thought, but perhaps an effort at a LAD HIG (Human Interface<br>> Guidelines) might be a good idea, so things like this aren't arbitrarily<br>> different between apps and plugins?<br>> <br>> Naturally the scope of such a thing would be limited since different<br>> programs have different needs, but at least things like twiddling<br>> parameters could easily be standardized.<br><br>That is a good idea. The recent comments on the use of Shift vs Control<br>and controller changes does highlight some differences. Bristol uses<br>Shift for accelerator (as in shift your butt) and Control as a decelerator<br>to have more control of what is being changed but that was an pretty<br>arbitrary choice I made a while ago.<br><br>Which ever seem reasonable/practicable to the group here might also<br>want to consider the kind of values that Shift/Control might have? Am <br>not advocating any preference, just giving examples: bristol/brighton<br>use Shift to go from min to max in 16 steps - ie, reasonably quickly.<br>Control does the same motion in 256 (I might have actually changed<br>that a while ago). Up/Down on their own increment by 1/16384th, that <br>is my best resolution due to using an extraction of MIDI 7bit, dual digit <br>encoding for the transfer syntax. The behavious is pretty anomalous or<br>arbitrary, that is admitted. <br><br>Most of the keyboard accelerators I use are based on U/D/L/R Arrow<br>and H/J/K/L 'vi' style controls. <br><br>I have no objection to changing them especially if it is a generally agreed<br>set of changes and a coherent proposal.<br><br>There are diverse other issues that might need to be considered such as<br>how to handle lin vs log controls?<br><br>Kind regards, nick<br></div> </div></body>
</html>