yes, it works fine!<br><br><div class="gmail_quote">On 6 March 2012 17:12, Roman Haefeli <span dir="ltr"><<a href="mailto:reduzent@gmail.com">reduzent@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Tue, 2012-03-06 at 10:56 -0500, Hans-Christoph Steiner wrote:<br>
> On Mar 4, 2012, at 9:45 AM, Roman Haefeli wrote:<br>
</div><div class="im">> > Actually [zexy/makesymbol] wasn't ever used in [arduino], only in<br>
> > arduino-help.pd . There it's used to display the Firmware version in a<br>
> > GOP cnv object -> [zexy/makesymbol firmata_%s.%s]. This can be safely<br>
> > replaced nowadays by [symbol firmata_$1.$2(. However, I didn't even use<br>
> > that, because I thought it would be useful to display the whole Firmata<br>
> > specification there, not only the protocol version. It now displays<br>
> > something like:<br>
> ><br>
> > StandardFirmata 2 3<br>
> ><br>
> > and it does so with only using vanilla classes. Let me point that<br>
> > [arduino] itself is not all affected by this.<br>
><br>
> Replacing [zexy/makesymbol] sounds like a good solution. I think that<br>
> the [symbol Firmata_$1.$2( will produce the most readable version of<br>
> this. "StandardFirmata 2 3" is not super clear, especially to<br>
> newbies.<br>
<br>
</div>Why would like the help-patch to only show the version in some weird<br>
format instead of showing exactly what [arduino]'s right outlet is<br>
sending? Am I missing something here? It's easy to change, but I don't<br>
get your point here. If you insist, i'll change it.<br>
<div class="im"><br>
> >> Pduino deliberately uses namespace prefixes because that's currently<br>
> >> the only way to guarantee the correct object is being loaded.<br>
> ><br>
> > Agreed.<br>
> ><br>
> >> Using [declare -lib zexy] [makesymbol] does not currently guarantee<br>
> >> that (tho it should).<br>
> ><br>
> > Yeah, I also agree that it should.<br>
> ><br>
> > Please, tell me about your further constraints, if there are any, and<br>
> > I'll see how I can comply with them.<br>
><br>
> I can't think of any off the top of my head, but I am sure they exist.<br>
> The best approach for something like this, I think, is to try to make<br>
> sure that the given output is exactly the same. So if the<br>
> [zexy/makesymbol] code produces "Firmata_2.3", the updated code should<br>
> as well, unless the problem is specifically because the message is<br>
> like "Firmata_2.3".<br>
<br>
</div>Sorry, if I am wrong, but I have the slight feeling, that you still<br>
think that something in [arduino] has changed. I can assure you that the<br>
updated [arduino] gives the _exact_ same output as the original one.<br>
That is, it still sends:<br>
<br>
'firmware StandardFirmata 2 3'<br>
<br>
'version 2 3'<br>
<br>
to it's right outlet. Only the help-patch has changed (see above).<br>
<br>
Please be assured, I wouldn't change any message format in [arduino]<br>
itself.<br>
<br>
So, how we proceed?<br>
<span class="HOEnZb"><font color="#888888"><br>
Roman<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
<a href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>
UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Jordi Sala<br><a href="http://musa.poperbu.net">http://musa.poperbu.net</a><br>