Bug. autopattr and textbutton
In an existing patch, created in Max 5.0, I get the error message:
autopattr: can only connect to a left inlet.
If I create a new textbutton, and try and connect the existing autopattr (either outlet 1 _or 2) to it, then I get the same message. So it looks like there's a problem with textbutton.
Any chance of an incremental fix soon? This breaks preset storage!
I take it all back. After a bit of fiddling around I found the top level autopattr was connected to the second input of a subpatch [p ] . Connecting _anything new to the autopattr brought the error message up. That's new, as I was (mistakenly) trying to read settings in the subpatcher through that inlet before (doesn't work) but I didn't used to get the error message.
So _something's different in 5.1, but all it did was point out a bit of duff programming on my part.
OK, there's still a problem, in that the state of any of the text buttons that are in my whole patch are not being stored or recalled.
Looking at the storage slots window, I can see that the correct state of the textbuttons is being stored.
If I change the state of a button then that is stored.
But if I change button state, and then recall without storing, the correct button state _isn't recalled.
I've tried this with my other two big patcher instruments, and can confirm that something about textbutton and pattrstorage is broken. None of the button states are being recalled or stored. As far as I can tell, this only affects textbutton.
I can reproduce that. The issue has been fixed for the next incremental version.
As in the next full incremental, or will there be an object incremental (nd where are those these days? I couldn't find them)
Hopefully whichever it is will be soon as none of my presets work any more!
thanks
Here's a mac version:
https://cycling74.com/download/textbutton_41232.zip
Fantastic. Thanks for that.
And the windows version:
https://cycling74.com/download/textbutton_41232W.zip
Sorry for any inconvenience.