vichug

so i have this strange bug, where a coll has its stored data saved with patcher, and this coll is named, and this name is also the name of a patcher in my Max file preferences paths. The coll then, when opening the patcher, remembers its saved datas, but also tries to read the .pat, and outputs this to Max window : "error in text file line 1". And when i double click on the coll, the data is the right saved data, but the titel of the window opened is with a .pat, and the icon is that of a max4 patcher.

I would have expected coll to be more clever thant that and not trying to read a .pat... is there a way to prevent him from doing this ? For now the only problem it results in is this red line on open in the max window, can it eventually lead to more serious issues ?

Also, what's the deal with all the spam... i have like 15 topics of spams, in which there are 3 topics that are copypasted 5 times each or so...common Cycling, no captcha or something ?...

so i have this strange bug, where a coll has its stored data saved with patcher, and this coll is named, and this name is also the name of a patcher in my Max file preferences paths. The coll then, when opening the patcher, remembers its saved datas, but also tries to read the .pat, and outputs this to Max window : "error in text file line 1". And when i double click on the coll, the data is the right saved data, but the titel of the window opened is with a .pat, and the icon is that of a max4 patcher.
I would have expected coll to be more clever thant that and not trying to read a .pat... is there a way to prevent him from doing this ? For now the only problem it results in is this red line on open in the max window, can it eventually lead to more serious issues ?

Also, what's the deal with all the spam... i have like 15 topics of spams, in which there are 3 topics that are copypasted 5 times each or so...common Cycling, no captcha or something ?...


a-named-coll-tries-to-read-a-patcher-file-pat

that is just how max works, sadly. accept or go crazy. the search path is master.

rename your patch, or rename your coll. no cake and eat. but simple to fix.

Adding a second argument prevents coll from looking for a file.

A named coll tries to read a patcher file (.pat)