dhjdhjdhj

I'm experimenting with jitter using Java and was testing out a simple sketch program I found here (

http://www.evsc.net/tech/how-to-jitter-java-objects)

Works fine when I define a [jit.window dum @size 290 200] but if I create a [jit.pwindow dum @size 290 200] I don't get anything displayed. I was under the impression that other than creating separate window/embedded in patcher window, these objects behaved identically.

I've never needed to work with jitter before so I apologize if I'm asking a question for which the answer is trivial.

I'm experimenting with jitter using Java and was testing out a simple sketch program I found here (http://www.evsc.net/tech/how-to-jitter-java-objects)

jit-window-vs-jit-pwindow

did you create your pwindow in addition to your window? you can't have two gl drawing contexts with the same context name.

if you want to display in both your pwindow and your widow, you need to create a shared context. follow the instructions here:

https://cycling74.com/wiki/index.php?title=OpenGL_Preview_Window

and even simpler with max 7 and jit.world:

did you create your pwindow in addition to your window? you can't have two gl drawing contexts with the same context name.
if you want to display in both your pwindow and your widow, you need to create a shared context. follow the instructions here:
https://cycling74.com/wiki/index.php?title=OpenGL_Preview_Window

and even simpler with max 7 and jit.world:


Thanks so much for your response --- after looking at your example, and in particular playing with that [attrui] object, which I've never used before, I figured out that I was not setting the name of the pwindow properly. Rather strange that you set the name of a jit.window with an argument but you have to use an attribute to set the name of a jit.pwindow

Thanks so much for your response --- after looking at your example, and in particular playing with that [attrui] object, which I've never used before, I figured out that I was not setting the name of the pwindow properly.  Rather strange that you set the name of a jit.window with an argument but you have to use an attribute to set the name of a jit.pwindow


typing "jit.pwindow @name pwinctx" into a new object box should work fine.

Yes, that's what I figured out after looking at your earlier code. I was just surprised that I had to specify the name as an attribute when, with a jit.window, I was able to use a regular argument value

Yes, that's what I figured out after looking at your earlier code. I was just surprised that I had to specify the name as an attribute when, with a  jit.window, I was able to use a regular argument value


jit.window vs jit.pwindow