Stefan Tiedje

Whenever I script an object within a bpatcher, it will be positioned 

relative to the main patcher, which renders scripting of visible objects 

I wanted to move a slider two pixels to the right, and it was moved way 

load the below patcher into a bpatcher and place it more to the right...

click the script, watch the slider disapear.

move according to the internal coordinates of the bpatcher as it does 

If there would be a way to get the information about the properties 

(position and size) of a bpatcher into the bpatcher, I could patch 

Max 4.6.1, OS X 10.4.7, Powerbook 12" PPC

Whenever I script an object within a bpatcher, it will be positioned 
relative to the main patcher, which renders scripting of visible objects 
useless within a bpatcher.

I wanted to move a slider two pixels to the right, and it was moved way 
out of sight.

steps to reproduce:
load the below patcher into a bpatcher and place it more to the right...

expected result:
move according to the internal coordinates of the bpatcher as it does 
with normal patchers...

possible workaround:
If there would be a way to get the information about the properties 
(position and size) of a bpatcher into the bpatcher, I could patch 
around that problem.

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


bpatcher-scripting-bug

This is pretty standard fair. just about all of the coordinates and 

scrolling is done relative to the main patcher. I think its a tad 

counter intuitive but its been discussed before. obviously the work 

around is to get and use the top/left coordinates of the bpatcher.

if your not in js jasch's posit object should do the trick

other than that, I give the floor to a more senior maxman

This is pretty standard fair.  just about all of the coordinates and  
scrolling is done relative to the main patcher.  I think its a tad  
counter intuitive but its been discussed before.  obviously the work  
around is to get and use the top/left coordinates of the bpatcher.

other than that, I give the floor to a more senior maxman
-matt


> if your not in js jasch's posit object should do the trick

Thanks to the pointer. If somedy has a js solution to get the 

coordinates of a bpatcher, that would be great as well...

For the relative moving its actually not a problem as I found the offset 

The other workaround is to place all potential objects in there and 

delete those which are not needed. Thats what I do now...

matthew aidekman wrote:
> if your not in js jasch's posit object should do the trick

Thanks to the pointer. If somedy has a js solution to get the 
coordinates of a bpatcher, that would be great as well...

For the relative moving its actually not a problem as I found the offset 
scripting command.
The other workaround is to place all potential objects in there and 
delete those which are not needed. Thats what I do now...

put this into a javascript inside your bpatcher (it works for 

>> if your not in js jasch's posit object should do the trick

> Thanks to the pointer. If somedy has a js solution to get the 

> coordinates of a bpatcher, that would be great as well...

*    get the coordinates of the bpatcher box - jasch 20060914

    outlet(0, this.patcher.box.rect);

put this into a javascript inside your bpatcher (it works for  
subpatchers in general).

>> if your not in js jasch's posit object should do the trick
>
> Thanks to the pointer. If somedy has a js solution to get the  
> coordinates of a bpatcher, that would be great as well...

/*
*	get the coordinates of the bpatcher box - jasch 20060914
*/

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

> put this into a javascript inside your bpatcher (it works for 

Thanks a lot, much simpler than I thought...

/*j wrote:
> put this into a javascript inside your bpatcher (it works for  
> subpatchers in general).
>
> this.patcher.box.rect

Stephan - the other method is to use the offsetfrom var, var2 method 

to thispatcher, and use a hidden named object within the bpatcher to 

the problem with this solution is that it only gets the box 

coordinates from within the bpatcher, relative to the bpatcher, as 

if I have an ubumenu within the bpatcher, and I want to get its 

global , absolute coordinates relative to the screen, how do I do it? 

I posted this question recently in the JS forum. Any help?

BTW, that bpatcher coordinate issue is really really really non- 

intuitive, and IMO should be fixed. or set as an option in the 

bpatchers inspector to choose the coordinate system.

On Sep 14, 2006, at 6:04 AM, Stefan Tiedje wrote:

>> put this into a javascript inside your bpatcher (it works for 

> Thanks a lot, much simpler than I thought...

Stephan - the other method is to use the offsetfrom var, var2 method  
to thispatcher, and use a hidden named object within the bpatcher to  
use as your new origin.

the problem with this solution is that it only gets the box  
coordinates from within the bpatcher, relative to the bpatcher, as  
far as Ive seen on my max 4.6.1.

if I have an ubumenu within the bpatcher, and I want to get its  
global , absolute coordinates relative to the screen, how do I do it?  
I cant seem to figure it out ...

BTW, that bpatcher coordinate issue is really really really non- 
intuitive, and IMO should be fixed. or set as an option in the  
bpatchers inspector to choose the coordinate system.

> /*j wrote:
>> put this into a javascript inside your bpatcher (it works for   
>> subpatchers in general).
>>     this.patcher.box.rect
>
> Thanks a lot, much simpler than I thought...
>
> Stefan
>
> -- 
> Stefan Tiedje------------x-------
> --_____-----------|--------------
> --(_|_ ----|-----|-----()-------
> -- _|_)----|-----()--------------
> ----------()--------www.ccmix.com
>

bpatcher scripting bug