Thomas,<br><br>Wow, that fixed everything! Just added "py" to startup items and now everything loads & runs perfectly - thank you so much!<br><br>Have you thought about mentioning this in the README? This was a very obvious solution that I didn't think of, but it might help others in the same situation...
<br><br>Thanks again,<br><br>David<br><br><div><span class="gmail_quote">On 2/18/06, <b class="gmail_sendername">Thomas Grill</b> <<a href="mailto:gr@grrrr.org">gr@grrrr.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi David,<br><br>> By "couldn't create", it means the [pyext] object fails to start, and<br>> has a dashed border around it - pd doesn't recognize the name.<br>><br>><br>> A search of my directory tree couldn't find any files called pyext.*,
<br>> so not only are they not in the correct path, they don't exist at all<br>> on my machine. However, there is a py.dll binary in pd/extra/, and pd<br>> sees it just fine. Could it be that pyext.dll failed to compile from
<br>> the CVS sources?<br><br>pyext is an object within the py library (which contains the py, pyext<br>and pym objects). You have to load it by including it into the PD<br>startup items (startup menu). Just add py there (in former times, this
<br>was the "-lib py" startup option).<br>In your previous message, you obviously tried to use py before pyext,<br>which resulted in loading of the library (because of the similar name).<br><br>><br>> As far as "doesn't work correctly," when I use an example patch with
<br>> [py], changing the input to the [py] object doesn't have any effect on<br>> the output. Quite simply, it does nothing - it doesn't work.<br>><br><br>I'd be very surprised about that. When you add the py/scripts folder to
<br>the PD path, open the script-1.pd example patch, and then click onto<br>[list H e l l o(, what is output on the console?<br><br>best greetings,<br>Thomas<br><br></blockquote></div><br>