PD's gui won't be slow if the code in the object won't awkwardly composed, for exemple using hundreds of toggles or radiobuttons for building a sequencer interface is awkward when there is an high amount of other solutions that uses a lower number of gui interfaces.<br> <br> I've seen many pd users using a different graphical instance for every fonction, when a single graphic interface and a bunch of buttons can do the same work for the whole thing. <br> And datastructures won't suck the cpu as much as pd gui interfaces does.<br><br><b><i>hard off <hard.off@gmail.com></i></b> a écrit :<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> from my experience, pd is REALLY slow at anything with gui's.<br><br>compared to the limited functions they have, pd's gui interfaces<br>always use so much cpu.<br><br><br> </blockquote><br><p>
                <hr size=1>
Nouveau : téléphonez moins cher avec Yahoo! Messenger. <b>Appelez le monde entier à partir de 0,012 euros/minute !</b>
<a href="http://us.rd.yahoo.com/messenger/mail_taglines/gmail/*http://fr.beta.messenger.yahoo.com">Téléchargez</a> la version beta.