Roman Thilenius

two issues, maybe someone has an idea what causes this.

i have a top level patcher which contains 200 bpatchers, and in the bpatcher there are 3 GUI objects, one of them is a picturecontrol, dialmode, has mask.

the picturecontrol works fine, the bpatcher works fine, and when i load the complete top level patcher the bpatchers and their content also loads correctly.

but when another huge patcher is already open, that same top level patcher does NOT initialize correctly: all the dials do not load. the image is not visible, and the dial does not have any function either.

while i understand why it can be difficult to load 200 times the same picturefile from disk via loadbang - and how to solve it - i am overwhelmed why it can make a difference whether that other patcher is already open or not.

that other patcher does not consume CPU, does not have a running metro, and does not do anythign to the harddisk. the two top level patchers are NOT opened together.

all it does is that it exists (which means that it is fragmenting the RAM a lot in MacOS9).

(i can not test it under other max versions, because my OSX and windows computers are of course a lot faster and wont reproduce the error at all - i tried with up to 1000 bpatchers)

when that top level patcher with the 200 bpatchers with the picture dial is opened alone, and pretends to work 100%, at one point it still does not.

the 2 lowest bpatchers - despite they show the graphics - always have dead dials, which can not be moved by the mouse.

aha, you might say, those are the two which were loaded first on init!

wrong. when i move them in the middle of the screen, ALL 200 work properly.

as soon as i move any of the bpatchers lower than 1100 pixels (screen is 1200 heigh and the top level patcher is in fullscreen), no matter if 1, 2 or 3 bpatchers, they dont work.

when you move them a bit up again, reload the patch, they work fine again.


two issues, maybe someone has an idea what causes this.

1.)
i have a top level patcher which contains 200 bpatchers, and in the bpatcher there are 3 GUI objects, one of them is a picturecontrol, dialmode, has mask.

the picturecontrol works fine, the bpatcher works fine, and when i load the complete top level patcher the bpatchers and their content also loads correctly.

but when another huge patcher is already open, that same top level patcher does NOT initialize correctly: all the dials do not load. the image is not visible, and the dial does not have any function either.

while i understand why it can be difficult to load 200 times the same picturefile from disk via loadbang - and how to solve it - i am overwhelmed why it can make a difference whether that other patcher is already open or not.

that other patcher does not consume CPU, does not have a running metro, and does not do anythign to the harddisk. the two top level patchers are NOT opened together.

all it does is that it exists (which means that it is fragmenting the RAM a lot in MacOS9).

so what can cause this difference?

(i can not test it under other max versions, because my OSX and windows computers are of course a lot faster and wont reproduce the error at all  - i tried with up to 1000 bpatchers)

2.)
even more weird is the following error.

when that top level patcher with the 200 bpatchers with the picture dial is opened alone, and pretends to work 100%, at one point it still does not.

the 2 lowest bpatchers - despite they show the graphics - always have dead dials, which can not be moved by the mouse.

aha, you might say, those are the two which were loaded first on init!

wrong. when i move them in the middle of the screen, ALL 200 work properly.

as soon as i move any of the bpatchers lower than 1100 pixels (screen is 1200 heigh and the top level patcher is in fullscreen), no matter if 1, 2 or 3 bpatchers, they dont work.

when you move them a bit up again, reload the patch, they work fine again.

wtf.



two issues, maybe someone has an idea what causes this.

1.)
i have a top level patcher which contains 200 bpatchers, and in the bpatcher t

loading-images-fails-loading-picture-control-fails

so as it turns out it is the fullscreen mode.

when TL patcher 1 is in fullscreen and you load TL 2, one the images in the bpatchers inside TL refuses to load.

and it does not only happen with the built-in fullscreen mode, it also happens with custom fullscreen window settings. 

it is _not the hidden menubar, i doubt it can be the size. so it must be the panel style ("notitle")

why would an image for picture control in a bpatcher not load only because _another window is in "notitle"?


so as it turns out it is the fullscreen mode.

when TL patcher 1 is in fullscreen and you load TL 2, one the images in the bpatchers inside TL refuses to load.

this is really nasty.

and it does not only happen with the built-in fullscreen mode, it also happens with custom fullscreen window settings. 

it is _not the hidden menubar, i doubt it can be the size. so it must be the panel style ("notitle")

why would an image for picture control in a bpatcher not load only because _another window is in "notitle"?


it also only happens with mask, and it happens only with my picture, with the picturecontrol help everything works. this is a bottomless pit.

loading images fails & loading picture control fails.