Tarik

When I have a jit.pwindow in the same subpatch as a jit.gl.slab, even if they're completely disconnected, jit.gl.slab behaves weirdly. It doesn't load jxs files correctly and produces incorrect data, even when no jxs is loaded. I've reproduced this bug on two different macs (osx 10.9.5 and 10.10) and max versions 6.1.8 and 6.1.9

anybody care to reproduce also? Just copy,paste, and click the toggle to see if the window changes from checker pattern to white.

bug-jit-gl-slab-pwindow

yes, reproduced here on 6.1.7 / OSX10.6.8

this is an unfortunate side effect of our implicit context detection feature.

when a gl object is instantiated in a patch without a context argument, it looks inside its current patch (and parent patches) for the first possible context to add itself to. in this case, it finds the pwindow first and adds itself to the pwindow context.

the solution is to either use explicit context names, or not include pwindows in patches that use implicit contexts.

in this case all you need to do is give your jit.window a name, and then provide that name as the first arg to the gl.slab in the wrong sub-patch, thereby forcing that slab to join the jit.window context, rather than the pwindow context.

this is an unfortunate side effect of our implicit context detection feature.
when a gl object is instantiated in a patch without a context argument, it looks inside its current patch (and parent patches) for the first possible context to add itself to. in this case, it finds the pwindow first and adds itself to the pwindow context.

the solution is to either use explicit context names, or not include pwindows in patches that use implicit contexts.
in this case all you need to do is give your jit.window a name, and then provide that name as the first arg to the gl.slab in the wrong sub-patch, thereby forcing that slab to join the jit.window context, rather than the pwindow context.


Ah of course, makes complete sense... thanks

always give your render destination a name

BUG - jit.gl.slab + pwindow