danieleghisi

Is there a way to retrieve the patcher exact name (not the path!) inside a patch?

retrieve-patcher-name

save as parentname.js and place it into a js object...

setoutletassist(0, "(symbol) 'parent name'");

setoutletassist(1, "(symbol) 'name of grandparentpatcher'");

outlet(0, this.patcher.parentpatcher.box.varname);

outlet(1, this.patcher.parentpatcher.parentpatcher.name);

inlets = 1;
outlets = 2;
setinletassist(0, "bang it");
setoutletassist(0, "(symbol) 'parent name'");
setoutletassist(1, "(symbol) 'name of grandparentpatcher'");

function bang()
{
    if(this.patcher){
        outlet(0, this.patcher.parentpatcher.box.varname);
        outlet(1, this.patcher.parentpatcher.parentpatcher.name);
   }
}


I hoped there could be some simple undocumented command for [thispatcher], but the js solution is fine.

Thanks a lot!!
I hoped there could be some simple undocumented command for [thispatcher], but the js solution is fine.


I tried this and got the following error (displayed in the Max window)

js: parentname: Javascript TypeError: this.patcher.parentpatcher has no properties, line 9

js: parentname: Javascript TypeError: this.patcher.parentpatcher has no properties, line 9
js: error calling function bang


For whatever it's worth, I needed a way to just get the name of the top-level patcher no matter how deeply embedded. After looking at the above and looking at the Patcher Properties example in the Max5 documentation, I finally ended up with this simplified version. Note that, rather than a bang, one sends in the message 'toplevelpatchername' to this thing. I did that because this code now lives in a file called PatcherUtils and will have other functions added as needed. I also noted that to use this implicitly in a patcher, the loadbang needed to go through a deferlow so that the new object (that calls this code) is fully connected to its parent.

while (p.parentpatcher) // If I have a parent, keep going up

For whatever it's worth, I needed a way to just get the name of the  top-level patcher no matter how deeply embedded. After looking at the above and looking at the Patcher Properties example in the Max5 documentation, I finally ended up with this simplified version. Note that, rather than a bang, one sends in the message 'toplevelpatchername' to this thing. I did that because this code now lives in a file called PatcherUtils and will have other functions added as needed. I also noted that to use this implicitly in a patcher, the loadbang needed to go through a deferlow so that the new object (that calls this code) is fully connected to its parent.

inlets = 1;
outlets = 1;
setinletassist(0, "Some message");

function toplevelpatchername()
{
   var p = this.patcher;
   while (p.parentpatcher)  // If I have a parent, keep going up
      {
         p = p.parentpatcher;
      }
   outlet(0, p.name);
}


retrieve patcher name