klaus filip

here is a simple bpatcher file to demonstrate, that thispatcher refuses to answer on the "window getsize" message,

when sitting inside a bpatcher. (which it perfectly did in max6)

please tell me, if this is a bug or a wanted new behaviour.

hi there,
here is a simple bpatcher file to demonstrate, that thispatcher refuses to answer on the "window getsize" message,
when sitting inside a bpatcher. (which it perfectly did in max6)
please tell me, if this is a bug or a wanted new behaviour.
thanks
klaus


thispatcher-in-bpatcher-does-not-report-window-size-any-more-in-max7

with 6 lines of javascript i am saved though ;)

    outlet(0,w.location[2]-w.location[0],w.location[3]-w.location[1]);

var w;
function get()
{
        w=this.patcher.wind;
	outlet(0,w.location[2]-w.location[0],w.location[3]-w.location[1]);
}


Klaus, thank you so much for this code! I noticed that, while it works, it doesn't output quite the same information that the original getsize message generates. I made some modifications so that you now get the exact same dimensions that you'd get from thispatcher

outlet(0,w.location[0],w.location[1], w.location[2], w.location[3]); 

var w; 
function get() 
{ 
w=this.patcher.wind; 
outlet(0,w.location[0],w.location[1], w.location[2], w.location[3]); 
}

ok, upon further testing, it looks like it's reporting the window size of the parent patch, not the actual bpatcher file itself

What about this?

function bang() {
outlet(0, this.patcher.box.rect);}

thispatcher in bpatcher does not report window size any more in max7