<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 07/30/2013 03:16 PM, Dan Wilcox
wrote:<br>
</div>
<blockquote
cite="mid:133B2602-2C31-4C0C-BB4D-C386408E1A64@gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>
<div>On Jul 30, 2013, at 2:55 PM, Jonathan Wilkes <<a
moz-do-not-send="true" href="mailto:jancsika@yahoo.com">jancsika@yahoo.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000">
<blockquote
cite="mid:7C124560-9D44-44C9-8A66-E99DBAE7C97F@gmail.com"
type="cite" style="font-family: Helvetica; font-size:
medium; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: 2; text-align: -webkit-auto; text-indent:
0px; text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; "><br
class="Apple-interchange-newline">
* the Apple interface guidelines generally frown on
"Apply" buttons like the "Connect" button in the
audio/midi dialogs. The expected behavior is that you also
connect when you select the device in the drop down, the
idea being you don't require 2 steps. At least that's how
I would do it. It's a niggle, but thought I'd throw it in.</blockquote>
<br style="font-family: Helvetica; font-size: medium;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; ">
<span style="font-family: Helvetica; font-size: medium;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255); display: inline !important; float: none; ">But
then what about the blocksize, samplerate, and callbacks?
If those don't immediately update then the user would have
to switch devs to get them to update. If they immediately
update then the user would need to press <tab> or
click somewhere to make the text entry lose focus. Both
of those seem problematic, but if there's an Apple-like
HIG solution I'll try to implement it.</span><br
style="font-family: Helvetica; font-size: medium;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; ">
<br style="font-family: Helvetica; font-size: medium;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; ">
<span style="font-family: Helvetica; font-size: medium;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255); display: inline !important; float: none; ">-Jonathan</span></div>
</blockquote>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Yeah, as I said, it's a niggle and more Mac specific but you
do it this way, for instance, in the GUI pane.</div>
<div><br>
</div>
<div>The Apply button concept is more firmly entrenched on the
other desktops. I really only understood that after writing a
Mac-only app and trying to make it work like the other native
apps. There are certain situations where you need to start and
stop things which does have a separate button. In some cases,
certain options are disabled (greyed out / deactivated) when
changing them has no effect and deactivated based on another
control, say starting/stopping some background process.</div>
<div><br>
</div>
<div>At the very least, I think "Connect" is a bit confusing. It
implies that there can be an unconnected state when the main
purpose of the dialog is managing which things are connected.
Maybe "Apply Settings", "Update Connection Settings", or even
"Update", etc is better.</div>
</blockquote>
<br>
Ok. I think "Update" or "Update Connection Settings" is probably
best.<br>
<br>
<blockquote
cite="mid:133B2602-2C31-4C0C-BB4D-C386408E1A64@gmail.com"
type="cite">
<div><br>
</div>
<div>Ok a few more now that I'm looking more closely:</div>
<div><br>
</div>
<div>* the MIDI channels text box should probably be filled by
default aka "16". Better yet, maybe it should be a drop down
box? Also, we weren't able to set the number of channels per
device in the old Midi settings dialog?</div>
</blockquote>
<br>
I'm a little restricted because I don't have any MIDI devices to
test with.<br>
<br>
<blockquote
cite="mid:133B2602-2C31-4C0C-BB4D-C386408E1A64@gmail.com"
type="cite">
<div>Does this mean we can split up channels now?</div>
</blockquote>
<br>
I haven't changed anything on the C side, nor really any of the
settings in the MIDI dialog.<br>
<br>
<blockquote
cite="mid:133B2602-2C31-4C0C-BB4D-C386408E1A64@gmail.com"
type="cite">
<div>Say use two devices but give them only 8 each? If we can't,
then maybe you don't need this text box.</div>
<div><br>
</div>
<div>* in the MIDI dialog pane, I get an error when I switch to
Multiple devices then back again: can't read "::midi_inchan2":
no such variable</div>
</blockquote>
<br>
Ok, sounds like a bug on my part. I'll check it out.<br>
<br>
<blockquote
cite="mid:133B2602-2C31-4C0C-BB4D-C386408E1A64@gmail.com"
type="cite">
<div><br>
</div>
<div>* in the Audio dialog pane, you could shorten "msec" to
"ms"IMO, and I would add some text to explain what "Use
callbacks" and "Delay" mean and why there's a setting for them.
Everything else makes sense really, but those always bothered
me.</div>
</blockquote>
<br>
Actually, I still have some work to do testing with Jack and
probably changing some of those settings when it's the API, because
I don't think "Delay" has an effect in that case.<br>
<br>
Also if you notice the "Help" window for the Audio dialog, you will
see I clearly explained "Use callbacks" with<br>
"???". :)<br>
<br>
I haven't looked at the API code closely enough to understand what
it does. If anyone can supply a nice<br>
user-facing explanation I'll add it.<br>
<br>
<blockquote
cite="mid:133B2602-2C31-4C0C-BB4D-C386408E1A64@gmail.com"
type="cite">
<div><br>
</div>
<div>* I wish the API dropdown box + "Number of devices" button
was centered like the content below it</div>
</blockquote>
<br>
Hm... I'll try that.<br>
<br>
<blockquote
cite="mid:133B2602-2C31-4C0C-BB4D-C386408E1A64@gmail.com"
type="cite">
<div><br>
</div>
<div>* The toggle nature of the "Use single/multiples devices"
never made sense to me. IMO is should really be a toggle button:
Use multiple devices? [x]</div>
</blockquote>
<br>
Ah, yes! That will help a lot on OSX, too-- a disabled button
doesn't really look disabled for some reason...<br>
<br>
<blockquote
cite="mid:133B2602-2C31-4C0C-BB4D-C386408E1A64@gmail.com"
type="cite">
<div> Better yet, there wouldn't need to be a direct control if
there was a [+] [-] mechanism in the device section itself. The
option would be implied: if you are</div>
<div> only using 1 device then yeah "Using single device", as
soon as you add a second one, then "Using multiple devices".
This makes sense for both </div>
<div> Audio and Midi. I know this is probably more work on the
GUI side, but I thought I'd bring it up from a UI point of view.</div>
</blockquote>
<br>
Yeah, that's probably the right way to do it.<br>
<br>
<blockquote
cite="mid:133B2602-2C31-4C0C-BB4D-C386408E1A64@gmail.com"
type="cite">
<div><br>
</div>
<div>* in the GUI dialog pane, I'd put the color swatch buttons
first, then the labels. This way they'd be aligned to the left
better.</div>
</blockquote>
<br>
That should be pretty easy to test out. I'll try it.<br>
<br>
Thanks for the feedback!<br>
<br>
-Jonathan<br>
<br>
<blockquote
cite="mid:133B2602-2C31-4C0C-BB4D-C386408E1A64@gmail.com"
type="cite"><br>
<div>
<span class="Apple-style-span" style="border-collapse: separate;
border-spacing: 0px; ">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space; "><span
class="Apple-style-span" style="border-collapse: separate;
color: rgb(0, 0, 0); font-family: Helvetica; font-size:
medium; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: 2; text-indent: 0px; text-transform:
none; white-space: normal; widows: 2; word-spacing: 0px;
border-spacing: 0px; -webkit-text-decorations-in-effect:
none; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; ">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
space; -webkit-line-break: after-white-space; ">
<div>--------</div>
<div>Dan Wilcox</div>
<div>@danomatika</div>
<div><a moz-do-not-send="true"
href="http://danomatika.com">danomatika.com</a></div>
<div><a moz-do-not-send="true"
href="http://robotcowboy.com">robotcowboy.com</a></div>
<div><br>
</div>
</div>
</span><br class="Apple-interchange-newline">
</div>
</span><br class="Apple-interchange-newline">
<br class="Apple-interchange-newline">
</div>
<br>
</blockquote>
<br>
</body>
</html>