Problem with [pattrstorage] names…
If I send [pattrstorage] a msg (from [sprinf]) that looks like "name MicChannel", that means the name field in the inspector and it’s storage windows should change to MicChannel, correct? Not happening. This is distinct from 1) the XML data file it may be reading, and 2) the scripting name (varname) in the inspector.
Anyone? Am I asking a dumb question or missing an easy answer? It has pretty much stalled everything…
I did a quick test and the name message does re-name the pattrstorage object, its just not immediately reflected in the clientwindow/storagewindow. Try renaming it and then closing/reopening the pattrstorage windows.
This does seem to change the scripting name as well as the ‘pattr name’. One solution would be to send the message [name pattrName]
followed by another message [sendbox varname scriptingName].
Oh, well that’s odd Had me chasing my tail for a good few days, but I *think* it’s worked out now (still confirming).
On a similar note, to change the scripting name of a patcher, I should just be able to send it the msg you indicated. If I’m correct, I should also be able to use send instead of sendbox and send the same msg to [thispatcher] and it will change the scripting name of whatever patcher [thispatcher] is in. But when I do that and then re-open the inspector, the scripting name doesn’t update. Is it changed or not, and what am I doing wrong?
This is getting a little frustrating, thanks for your help!
Thanks for bringing this up; it’s been fixed for the next release.
Which issue mentioned above are you referring to [pattrstorage] or the varname atribute? Glad to be able to contribute and that my questions are useful one way or another.
Changing the varname (Scripting Name from the Inspector) will now properly update pattrstorage’s name attribute. And changing pattrstorage’s name attribute (including by changing the box’s varname) will properly update the window titles.
Great, good to know. So this is a separate issue from the one above with varname and [thispatcher]?
I’m not really clear what you’re trying to accomplish with thispatcher. Are you trying to change the Global Patcher Name of a patcher (the pattrmarker name)? A quick look in the Inspector, turning on attribute names, shows that this attribute is called ‘globalpatchername’. Sending the message ‘globalpatchername foo’ to thispatcher does change this name. Maybe you can be more explicit about what you’re hoping to do. Patches which illustrate your problem, and how you’re trying to solve it, are a helpful tool for us — please take a few minutes and mock something up, so we can better understand your needs.
1. I needed to change a subpatcher’s (actually it’s abstraction in the larger patch this came from) scripting name, as tried on the top level of the patch below. Couldn’t get it to work.
2. I then realized for this need I would ideally change it from inside the subpatcher, so I figured I would use [thispatcher]. Also didn’t work.
3. I hadn’t heard of the ‘globalpatchername’ attribute and looked it up. Not sure it fits in if [pattrmarker] isn’t being used, or how it might be different than ‘varname’
4. Aside from the functionality stuff here, there is a larger issue about Max workflow at the bottom of this, but I put it in new topic in hopes of keeping things straight…
I have spent time with the documentation and searching the forum, which hopefully comes across, but am obviously still missing a thing or two. Hope this makes sense & many thanks,
----------begin_max5_patcher---------- 840.3oc0WsziaBCD9L7qvxq5ssqBFHOZOU06UpmiVEY.mD2BFD3jtsq1+60X yCaBvxp7nauXfwiwey2LdlwOaaACRehT.AeBrFXY8rskkTTo.qpusfI3mBiw ER0fLxuRC9A7d0TbxSbo3LvW2iYLRb8LrCITVLgKWkSkvsoLdA8ODoLzCyZ0 M8.uV4ZoYXd3dJa2lbRHWAwEyDqA3ndL2ubDIdG7X0RnQRvH.3GW.01SFNQt mvujSwMPTtAj7JisxZEKfFSNRxKnoLMraAaggub+W4IQgm7CukZ3Pvg6hSC+ IIRydrfQjsuk+QZFg0puTCiASMorrbRAgww7Jfquu3Cw7M8y9lyuEGRFbw8R iVvc4znTVIHLVYo35saMvQ45LvsTCFNqmEySSiCv4GoEzfXhgePDehYzDLmv oJ7fl0rNZRVNkwM9WFw3ZdZiXcC4ch4SHEE3cjZC1Hv2UWpQPORahAn9SC9c zlQIl+6rJJDBantANeLuhjkObQO3K9XoFi24LBB1Ahcbv0S9hsc8K2eEnvhv bZFGHBdi.Gw4kfnNaxZ2GeGxuKUOVsR80HD77aGCajXtCAKOSrELFQ+A5vLs y+LlVkkDgb6lpuKS679fo46oE0kUtnrIZT179IynHUd34qdUB80RNnMaA9XM Tt6akfwfF.vOWNb22KGEgdJIfGufdDI4NHgeshQUsgfTi90iCQnFAngoIIDU YJXegls0HiorgJdIgT478yPEoGxCqMl5rQ.S7EQJ3TVSKCqa88cTbOMJxrDs zIPixREoVp.3D8ouYbOUXO+cErclJci9eF2NWHbWITX.1M4Th1H1FwwsMXNO mFbfqNIn2rtnO6.bbUtllLTMsl1aKsWq9fGYpgZA2tkEjiJ+2YbOrlR8hDsh evHk4OianUq7voLG4xat9Z0gF51aNib6sKGYwAAffymNPCQGAX1txpcxmiQM 9RNYgirscuwHFzkkXLaKukYb5kUP2rfjY98eCFcpv6xREhzKbQ5swhFlnANQ 2sqxc69fyh4KWsR609rVecaRpfYqAJSrat9JC8jb795o3GJ8tgNmjYu+r5mP 5SEQH8ZICfHuaJh7l.G4bSQjyDPzhy.QhOdw9uvvOk0I -----------end_max5_patcher-----------
----------begin_max5_patcher---------- 653.3oc2VEsjZCBE84juBFlouYcRhF0su0oeFNNNjDTwRfL.Zscm8euDHIB6 lnYc5Cc2W.k6k68bOvIbeNL.lwufkPv2.qAAAOGFDXVpdgfl+G.KQWxoHowM HC+Kd1Q3DqoyHACUhMV9wADigoqmso0pBeQYLUAZL1ZoBoxOPX62Jv4Ja5Si mFMAjtrdbQZ8XRzzHvllcPJLQRm6utrMJ63LUW5+tff5hO6TIgQwJClicbWR 9iw83DcF57keR05bjKBwhFlngJzwfPwmwBIgybBc.7ZcjXAe5SlBYdT8z7UN khlg2S44+DW3ju.XAd26JH7JL65FLd3M36IgUIvRLSgTMP2MwnST019oGe66 P43A2buGEAv8BRAmUCBucVuba5VChMvN1C2FOXnpd1rhyoYHwYhjjQwdmD5q uHFoDovJhEOIQc6iTVIHLkWrvLjNFGj4BNk5EJqky8XwS13b+vS93s9sjQ9h kiRPykuZBUgkpoGktd1i3YQjUvXtuDmL+0xmWKghci2vmcCIktgbpGIk6lrK q9cUy4NDB1zZ8kvv1eL4Ao0RrTh1i6kWmMJNLNxLMKYZp9OqFlBSdPJL4CLE VWhf27c96PnqrSOYuadKFcwmTJ8Fhco46Q6.dL6WHijZSsSySuqdewmTAuAo 2grVF0RO5wz1wgnpECxEOdA6XNmWVhsu.Ag8PDWe9iRXC8FioHqs2OCI4mD4 souUYA7q3B86JDVW2.q6dW3U9cfTT3+3q4LfTTw0Wbav2HORe2vdrndw+UvN drrcxGYbG+OB2MKpK.ai2RzYbwVcZz52sHkRPxNorBAuFwuQCmTdFh5zCkUr Mp9YGbw60Y7.XYnlqCuxBlQCO7R3e4yuYmJ -----------end_max5_patcher-----------
Here’s the JS I used, save as patchernametest.js:
autowatch = 1;
var b = this.patcher.box;
b.varname = somename;
So then, in general, changing the varname (scripting name) of any patcher is not possible through conventional Max messages to [thispatcher], but it is with JS, correct?