<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:12pt"><div id="yiv4707200886"><div><div style="color:#000;background-color:#fff;font-family:arial, helvetica, sans-serif;font-size:12pt;"><div id="yiv4707200886yui_3_7_2_32_1369722651201_55"><span></span></div><div class="yiv4707200886yui_3_7_2_32_1369722651201_59" id="yiv4707200886yui_3_7_2_32_1369722651201_60" style="font-family:arial, helvetica, sans-serif;font-size:12pt;"> <div id="yiv4707200886yui_3_7_2_32_1369722651201_78" class="yiv4707200886yui_3_7_2_32_1369722651201_63" style="font-family:times new roman, new york, times, serif;font-size:12pt;"> <div id="yiv4707200886yui_3_7_2_32_1369722651201_77" dir="ltr"> <hr size="1"> <font id="yiv4707200886yui_3_7_2_32_1369722651201_76" face="Arial" size="2"> <b id="yiv4707200886yui_3_7_2_32_1369722651201_75"><span id="yiv4707200886yui_3_7_2_32_1369722651201_74"
style="font-weight:bold;">From:</span></b> Joćo Pais <jmmmpais@googlemail.com><br> <b id="yiv4707200886yui_3_7_2_32_1369722651201_152"><span id="yiv4707200886yui_3_7_2_32_1369722651201_151" style="font-weight:bold;">To:</span></b> "pd-list@iem.at" <pd-list@iem.at>; Jonathan Wilkes
<jancsika@yahoo.com> <br> <b id="yiv4707200886yui_3_7_2_32_1369722651201_148"><span id="yiv4707200886yui_3_7_2_32_1369722651201_147" style="font-weight:bold;">Sent:</span></b> Tuesday, May 28, 2013 2:34 AM<br> <b id="yiv4707200886yui_3_7_2_32_1369722651201_144"><span id="yiv4707200886yui_3_7_2_32_1369722651201_143" style="font-weight:bold;">Subject:</span></b> Re: [PD] Pd preferences dialog progress<br> </font> </div> <div id="yiv4707200886yui_3_7_2_32_1369722651201_90" class="yiv4707200886y_msg_container"><br>> Looks very nice. Can you show also the other sections of the dialog?<br><br>The GUI tab is just a placeholder for the moment. I don't have anything<br>hooked up there yet.<br><br>> One minimal detail: "Use single device" instead of "devices"<br><br>Yeah, that's bad but it could still be two devices which is why I wrote<br>it that (bad) way. I'll try to think of an improvement.<br><br>> A bigger detail: does it make
sense (for logical and practical reasons) to <br>add a menu to select which channels go into which inputs/outpus,
like on <br>max/msp?<br><br>Now that I've got the ttk styles down the frontend would take about 5 minutes<br>to make. Actually making it do something would take a lot longer, unless there's<br>a trick to it that one of the audio gurus knows about.<br><br>I may be wrong but that feature only seems important in making insane patches<br>sane. If you make an audio-producing patch in a maintainable way I imagine you'd<br>have everything ending up in a single [dac~] somewhere, especially a patch that's<br>massive-channel. In that case you could make an abstraction [ltop~] with<br>the same number of inlets as the [dac~],edit the [dac~] object box and make it<br>an [ltop~], then route the logical [inlets~] inside your abstraction to the physical<br>channels of a [dac~] inside it. It doesn't work if there are [dac~]s<br>sprinkled throughout a complex patch, but then that kind of patch probably doesn't<br>work anyway. :)<br><br>But if the
idea is to avoid editing the patch itself and instead edit the Pd instance,<br>maybe someone can write a gui-plugin to automate what I wrote above.<br>You'd right-click on a [dac~] and choose "map i/o" and it opens up a patch window<br>with [inlet~]s corresponding to the number of of logical inputs, with a [dac~]<br>sitting in the middle of the patch. That's a much better user-interface than a <br>big table. Do the same with [outlet~]s and [adc~] and you're done.<br><br>-Jonathan<br><br><br>> Hi List,<br>> I've made some progress on the centralized preferences dialog <br>> window. Screenshot attached show the appearance under X11.<br>><br>><br>> Progress:<br>> * dropdown menus modeled after gtk for GNU/Linux (ttk::combobox)<br>> * native dropdown menus for Windows (ttk::combobox)<br>><br>> * native-ish dropdown menus for OSX (ttk::menubutton)<br>><br>> * multi-device button
doesn't disappear when clicked (see attached <br>> audiodialog3.png)<br>> * audio api/settings/devices all in a single window<br>> * devices aligned in grid<br>> * removed cruft: unnecessary colons, device checkbuttons, label <br>> repetition<br>><br>> * multi-device button disabled when there aren't multiple ins/outs<br>> * single "connect" button to clarify when Pd is supposed to open audio<br>><br>> * can specify "None" as
device (same as unchecking the device in the old <br>> audio dialog)<br>><br>> * replaced "Apply" and "Ok" buttons with "Connect", which is more <br>> explicit. Also, it makes a nice<br>> flow from top to bottom: choose an api, the common audio settings, the<br>> specific devices (and device specific attributes: "channels"), and <br>> finally click "Connect". Connect also saves the audio settings-- I <br>> think that's generally what<br>> the user wants to do, and there can be a more general feature to make<br>> "profiles" if the user has a more complex/dynamic setup.<br>><br>><br>> I can also make it possible to specify no api (or a dummy one) if that's <br>> desirable.<br>><br>> Screenshots currently lack a "Close" button which will be common to all <br>> preference frames. (I.e., at the bottom of the dialog below the notebook <br>>
widget.)<br>><br>> For my own sanity the API dropdown list currently shows Pd's api number <br>> as well as the API name.<br>><br>><br>> -Jonathan<br><br><br></div> </div> </div> </div></div></div></div></body></html>