yade-dev team mailing list archive
-
yade-dev team
-
Mailing list archive
-
Message #00939
Re: r1658 - graphic display
-
To:
yade-dev@xxxxxxxxxxxxxxxxxxx
-
From:
Janek Kozicki <janek_listy@xxxxx>
-
Date:
Sat, 7 Feb 2009 05:36:51 +0100
-
Face:
iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAALVBMVEUBAQEtLS1KSkpRUVFXV1dYWFhjY2Nzc3N3d3eHh4eKioqdnZ24uLjLy8vc3NxVIagyAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAB3RJTUUH2AIVEzgS1fgQtQAAAjRJREFUOMtt1DFv00AUAOAzFQNbjigSyoQaRaBMhKgLUyKXpVNNeUpk9vyDqFJhQ1kiBuaqAwJCqvPtSLY7RlTn5+5IdnYkkt/AOyfxXVLe5vf53Z1875kd34tOEax8djmj6GyjhB5bxz50GdsVZr9fqRjZwAtKOJw5Wqs2MMZ16ALHsaDncF7xAHix1oEFHAB8f+pRjcO4gfZDykcYzbiucRolOLUJ6kjA0xtVt+A6TySlM0RajIpK6DzwKZ/nOYbF/gclHMo1ZOHYY/+Ha+AWuM+3oMS4eeqYzZ8FiCltgUqI8cd2wwAVpJk+8LWYjBtnJdQpHQqJMd4Oxt4bU9ESiFGc5hkqaH74asAX4iabP5I5gZ+qjgGlJCqZa3h3lxhoeVcSE1qLQC4sqKOK9MGW9E3izFqqHokoztLFEgXg31sbZEKnWi2T74A4NxfVQqlkjKtcAWD+zcArFEES01dR0E/nnV0IgugmDd/2L84sOAouRBBHEc7gtc8teDkRlE0iNQPo2w3Xhh/D4TCIQ4LRLoTvgwjj6RRgavdurxYGMaIuGOyAW/PpNlCcU9/93AHenAWYjPoAwa+G3e3to/MgFNTAEKvKDjzuCzHTnY3qqdXtx24VijzQfZ0yewZ5cwRFQaa+mIYr1uI0I76+3W4xhlvoVRwOA0Fdl64HlJnxP6T8YpX/Lga4Wv4A3ErrU5oTfN7Mu/llXMl8RXEPji/lQkN3H7qXqgC2By47EXeU/7PJ/wPxRKMnuZwIeAAAAABJRU5ErkJggg==
-
In-reply-to:
<7fd5f92b3fccc1f5f6e4dde7368c7420@arcig.cz>
> commit 1658
> 5. Adjust locks in GLViewer. Fixes my crashes on nvidia for both
> player and 3d view (didn't dare to try 2nd view). Next step will be
> to move this lock to Omega and lock it when loading/resetting
> simulation etc.
well. it still doesn't work for me. At least it doesn't hang, that's
an improvement. The 3d view is simply black. I have to work on snow
so I'm not working on it, I'm still simply just commenting out the
locks, because I need it to work :)
eudoxos said: (by the date of Tue, 03 Feb 2009 13:30:44 +0100)
> > commenting out that lock in GLViewer::paintGL(void) solves the problem.
>
> That doesn't solve the problem I was trying to solve, i.e. concurrent
> access from different threads.
>
> Did you try running scripts/gl-test.py (and enable second view therein)?
> There is the problem demonstrated. Please try rather commenting out
> makeCurrent/doneCurrent in lock constructor/desctructor. The lock itself is
> neede, see those threads on the subject:
>
> http://www.vtk.org/pipermail/vtkusers/2008-July/096077.html
> http://lists.trolltech.com/qt-interest/2006-06/thread00248-0.html
> http://doc.trolltech.com/qq/qq06-glimpsing.html
I'll check this out in few weeks, sorry. In fact I hope that you will
figure it out before it catches my attention ;>
--
Janek Kozicki |
Follow ups
References