this thread is getting a bit funny and people start to be afraid about [makesymbol] being deprecated ;-)
as i understand IOhannes, there is nothing wrong with [makesymbol] (nor with any other proposed solution). i think, he just wanted to point out that when externals are involved anyway - [makesymbol] from zexy in that specific case - , one could also use [l2s] - also from zexy - for that task, which could be considered as more straight forward. i assume, it was never meant to say, that [makesymbol] will be kicked out from zexy with growing (>0.40) pd version nor with growing zexy versions (actually 2.1 iirc). so, take the solution of your choice: [makesymbol]: needs zexy [makefilename]: a bit more complicated (see franks suggestion), but works only with internals [l2s]: needs zexy as well [$1$2(: only internals, but works only with pd >= 0.40 i hope, i could make things a bit clearer now. roman On Thu, 2007-04-05 at 20:05 +0200, Steffen wrote: > On 05/04/2007, at 16.12, hard off wrote: > > > i have so many patches with makesymbol constructs. personally i hope > > it stays in there just so i don't have to go and redo them all when i > > upgrade to 0.40 > > makesymbol is zexy. So you won't loose if you upgrade Pd and keep > zexy. If im not mistaken. Unless you mean that makesymbol was kicked > out of zexy version 0.40 and then got back in later on. This is > getting hairy. > > _______________________________________________ > [email protected] mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list ___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
