after an other Gem update, i found a problem
it concern most (all) primitive, and even other object (pix_video by example)
when this objets are create after the windows creation, they did not really work. you have to destroy/create the Gem window in order to see a new primitive.
this cause major problem, i'll have to revert to an older gem version until it is fixed...
are you trying to implement multiple windows?
Cyrille
cyrille henry wrote:
after an other Gem update, i found a problem it concern most (all) primitive, and even other object (pix_video by example)
when this objets are create after the windows creation, they did not really work. you have to destroy/create the Gem window in order to see a new primitive.
this cause major problem, i'll have to revert to an older gem version until it is fixed...
ouch. fixed now. the problem was M$ VisualStudio not liking my initialization code thus resulting in code that did not initialize a state-variable. it's now initialized explicitely.
any more problems?
are you trying to implement multiple windows?
yes. at least i'm trying to get the code in a state where multiple windows are at least theoretically possible :-)
fgmasdr IOhannes
IOhannes zmölnig a écrit :
cyrille henry wrote:
after an other Gem update, i found a problem it concern most (all) primitive, and even other object (pix_video by example)
when this objets are create after the windows creation, they did not really work. you have to destroy/create the Gem window in order to see a new primitive.
this cause major problem, i'll have to revert to an older gem version until it is fixed...
ouch. fixed now.
thanks
the problem was M$ VisualStudio not liking my initialization code thus resulting in code that did not initialize a state-variable.
oups
it's now initialized explicitely.
ok
any more problems?
don't see any for now. i'll tell you if i found some more...
are you trying to implement multiple windows?
yes.
nice!
at least i'm trying to get the code in a state where multiple windows are at least theoretically possible :-)
ok. thanks a lot Cyrille
fgmasdr IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
IOhannes zmölnig a écrit :
any more problems?
well example : 10.glsl/09.GPGPU_... start gem windows : ok close it and start again.
i've got at each frame lot's of : error: GEM-Xwin: BadDrawable (invalid Pixmap or Window parameter)
but the patch still work after initialising the shader. it is the only patch that does not work after windows destruction / creation.
i don't understand why the problem is specific to this patch, since it is only a more complex version of what's in other examples.
tell me if that is related to what you're doing now, or if i should digg to find more specifically where the problem comes from.
thx C
On Fri, 2010-01-29 at 09:58 +0100, IOhannes zmölnig wrote:
are you trying to implement multiple windows?
yes. at least i'm trying to get the code in a state where multiple windows are at least theoretically possible :-)
Kool! This sounds exciting!
Roman
Roman Haefeli escribió:
On Fri, 2010-01-29 at 09:58 +0100, IOhannes zmölnig wrote:
are you trying to implement multiple windows?
yes. at least i'm trying to get the code in a state where multiple windows are at least theoretically possible :-)
Like just putting more than one [gemwin] each one controlling a window?
Wow, that would be great!!
Hello,
Le vendredi 29 janvier 2010 à 12:36 +0100, cyrille henry a écrit :
IOhannes zmölnig a écrit :
any more problems?
well example : 10.glsl/09.GPGPU_... start gem windows : ok close it and start again.
i've got at each frame lot's of : error: GEM-Xwin: BadDrawable (invalid Pixmap or Window parameter)
I also get this error in my recent patch with Pd 0.42.5 and GEM 0.92.3 on Ubuntu 10.04. However, the patch is working as expected. IOhannes, do you have any informations about this error ? Thanx. ++
Jack
but the patch still work after initialising the shader. it is the only patch that does not work after windows destruction / creation.
i don't understand why the problem is specific to this patch, since it is only a more complex version of what's in other examples.
tell me if that is related to what you're doing now, or if i should digg to find more specifically where the problem comes from.
thx C
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev