[maxmsp] Re: simple questions about coll

Sure, I understand that. My point is more that offhandedly mentioning 
that 'xxxx crashes Max' doesn't help anyone, whereas taking a little 
time to prepare and submit support requests is useful all around. We 
don't ever ship software with known bugs, so if you're having a problem, 
we probably don't know about it! Let us know...

jb

Bas van der Graaff wrote:
> Oh, and i'd definitely be interested in the pattrstorage bug as well. I read in some other thread that a memory leaking issue has been fixed a while ago, and i haven't been able to crash it since (although i haven't spent a great deal of time trying). 
> 
> But it's probably too much work to change everything back to pattrstorage now anyway, coll really isn't that bad of a replacement. It requires you to make some of the functionality of pattrstrorage yourself but it also provides more control and flexibility (and you don't have to use object names), so it's not all bad.
> --
> SmadSteck - http://www.smadsteck.nl
> Hard- and software for interactive audiovisual sampling
> _______________________________________________
> maxmsp mailing list
> maxmsp at cycling74.com
> http://www.cycling74.com/mailman/listinfo/maxmsp