On Mon, 2010-07-12 at 20:34 -0400, Mathieu Bouchard wrote: > On Tue, 13 Jul 2010, cyrille henry wrote: > > > yep. cyrille > > is yours supposed to be working in pd-extended ? > even when adding "iemmatrix" directly to the library list, > > mtx_./ > ... couldn't create > mtx_.* > ... couldn't create > mtx_.* -1 > ... couldn't create > mtx_.* 0 > ... couldn't create > mtx_+ > ... couldn't create > mtx_./ 1 > ... couldn't create > mtx_.^ 0.5 > ... couldn't create > > does it work with a more recent version ? how recent does it have to be ? >
I added all missing aliases, so that using those names works directly also in Pd-extended's libdir format, without having to use any quirks as loading [mtx_add] before [mtx_+]. Unfortunately, Hans is not comfortable with auto-enabling hexloader, so in order to be able to use those aliases, you need an [import hexloader iemmatrix] in order to take advantage of those aliases. Even I, who already discussed with Hans about the issue with en/disabling hexloader on default, first forgot to enable it manually, which made me think, that the aliases are not working. I still think, that _not_ enabling hexloader causes more confusion than simply loading it on default. I thought I delivered enough proof that it is not causing any harm. So, using an rc4 autobuild and putting an [import hexloader iemmatrix] (iemmatrix is not loaded per default) should work. Roman _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list