Recent changes to feature-requestshttp://sourceforge.net/p/pure-data/feature-requests/2015-07-11T03:53:01ZOption to rescan Midi Devices?2015-07-11T03:53:01Z2015-07-11T03:53:01ZWilliam Hustonhttp://sourceforge.net/u/williamahuston/http://sourceforge.net567a1f277763c981d40c9e8bad5477ad965af82a<div class="markdown_content"><p>I am using PD 0.43.4-extended on Windows 7. </p>
<p>If I start PD without my MIDI controller attached, there is nothing I can find to get PD to see it. I must start PD with the MIDI controller attached. </p>
<p>Is it possible to ask PD to "rescan MIDI devices" while it is running? </p>
<p>Thanks<br />
BH</p></div>#142 PD on Raspbery Pi 22015-02-21T18:09:33Z2015-02-21T18:09:33ZIOhannes m zmölnighttp://sourceforge.net/u/zmoelnig/http://sourceforge.netc095a0bb0ae5f333792620aca4031643a40c3f86<div class="markdown_content"><p>so what is wrong with <code>apt-get install puredata</code>?</p>
<p>are you just missing some external to address GPIO?</p></div>PD on Raspbery Pi 22015-02-21T13:48:04Z2015-02-21T13:48:04ZAnonymoushttp://sourceforge.net/u/userid-None/http://sourceforge.net8424f6816fa0b27ccf83dd8dec21bd526c666bdd<div class="markdown_content"><p>Would like to see current PD working on a Raspberry Pi 2 with GPIO.</p>
<p>Perhaps it is possible to take advantage of the faster quad-core CPU</p>
<p>ALSO!!!!<br />
GPIO starting addresses have moved and DMA has changes<br />
breaking real world interfacing</p></div>Advanced Code-Comment/Documentation Posibilities2014-11-09T11:41:18Z2014-11-09T11:41:18ZAnonymoushttp://sourceforge.net/u/userid-None/http://sourceforge.netf4d3dc3a0700caf8d3f378027ca1cd89a9360014<div class="markdown_content"><p>Hey,</p>
<p>what I really miss in PD is the opportunity for proper code-comments and code-documentation.</p>
<p>At this point it would be very useful, to write a comment-tag for every object.<br />
(Like it's implemented for number-objects).<br />
At the moment, I have to place an extra comment-object beside a message-object to comment their behavior. Thats pretty circuitous, because if I want to move the message-object, I also have to move the separate comment.</p>
<p>Furthermore it would be pretty cool, if one could change the color of each object.<br />
(Like it's implemented for switches).<br />
With this option it would be possible to mark coherent or very important parts of the code in different colors.</p>
<p>Another big enhancement for clarity would be the opportunity to format comments.<br />
For example to change the comment color, or to format comments bold or underlined.<br />
At the moment I have to position the comment and a copy of itself stacked, to achieve a pseudo bold effect. But that's pretty laborious.</p>
<p>I would be very happy, if some of the features could be implemented in PD.</p></div>iemgui positioning with autopatch2014-09-19T07:30:39Z2014-09-19T07:30:39ZGilberto Agostinhohttp://sourceforge.net/u/gilbertohasnofb/http://sourceforge.net2678b2b3b52d88a79323547af82e87409f2bb2da<div class="markdown_content"><p>Some of the iemgui objects, such as <span>[vsl]</span> and <span>[hsl]</span>, display buggy behaviours when used with autopatch. With autopatch on, if one selects an object, message, atom, etc. and then type Ctrl+1 &lt;ENTER&gt; hsl &lt;ENTER&gt;, the horizontal slider position is not centralized. The same is true for an object created after a <span>[hsl]</span> or <span>[vsl]</span> via autopatch.</p>
<p>See: <a href="http://s9.postimg.org/idpjzmxvj/Screenshot_from_2014_09_19_09_28_59.png" rel="nofollow">http://s9.postimg.org/idpjzmxvj/Screenshot_from_2014_09_19_09_28_59.png</a></p>
<p>I do understand that changes in the positioning of iemgui objects would cause legacy problems, but a possible solution would be to distribute a conversion script together with newer versions of pd and pd-extended. It would be relatively simple to write a script that would add or remove offset to certain objects.</p>
<p>This type of solution has been implemented before in other projects I am interested, such as with LilyPond whenever they decide to change the syntax. </p></div>#139 add initbang to pd vanilla2014-09-14T03:08:00Z2014-09-14T03:08:00ZSebastian Shaderhttp://sourceforge.net/u/sebfumaster/http://sourceforge.net65314b829682dc5691914acb8614c3f8e2ff8171<div class="markdown_content"><p><a href="https://sourceforge.net/p/pure-data/pd-extended/ci/c26bb57a28f350fade604a875b9d299900a9557d">https://sourceforge.net/p/pure-data/pd-extended/ci/c26bb57a28f350fade604a875b9d299900a9557d/</a></p></div>add initbang to pd vanilla2014-09-14T03:06:25Z2014-09-14T03:06:25ZSebastian Shaderhttp://sourceforge.net/u/sebfumaster/http://sourceforge.net30078bc25e92307f1657fe06a0072bc8d4e08892<div class="markdown_content"><p>it would be very helpful in dynamic patching!</p></div>#138 make every literal number in expr a float2014-06-17T07:35:40Z2014-06-17T07:35:40ZIOhannes m zmölnighttp://sourceforge.net/u/zmoelnig/http://sourceforge.netf5fe3c07135fdb822eae891fafa16a87f22fc2a9<div class="markdown_content"><p>i think the reasoning for the current behaviour is compatibility with older versions of expr (in Pd, jmax and Max/MSP).</p></div>#138 make every literal number in expr a float2014-06-16T22:11:03Z2014-06-16T22:11:03ZAnonymoushttp://sourceforge.net/u/userid-None/http://sourceforge.net5dc72549b6bebe55678d2cd67ddd138421490763<div class="markdown_content"><p>...or perhaps just for division</p></div>make every literal number in expr a float2014-06-16T20:44:02Z2014-06-16T20:44:02ZAnonymoushttp://sourceforge.net/u/userid-None/http://sourceforge.net93600f47ecbb09472e7511c926f90bf96204bd2a<div class="markdown_content"><p>right now every literal int given to an expr object remains an int, however since pd has no int type this makes no sense, right? If these literal ints are in an operation with a value passed from pd it will be converted to float anyways, and in an integer division operation integers will come out, so instead the user could just supply that result as a float. It's a small thing that might not be worth fixing, and it would move a bit farther away from c</p></div>