Hi all -- Another one of the examples that forces SingleThreaded is
osgdepthpartition. I keep intending to rewrite it using CompositeViewer with
ordered view processing, but haven't gotten around to it yet.

In a nutshell, if any code executed by the cull or draw threads (such as
your own callbacks or custom nodes) isn't thread safe, then you must use



        From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jason
        Sent: Thursday, April 17, 2008 11:40 AM
        To: osg users
        Subject: [osg-users] When must you use SingleThreaded threading
        Hi Robert,
        I was looking through the examples and noticed that osgphotoalbum,
osgdistortion and a few of the other examples are explicitly setting the
viewer to SingleThreaded threading model.  Is there anything inherit in
those examples where you *must* use the SingleThreaded viewer model rather
than the others?  Just curious as I'm trying to get my head around the new
OSG threading models.

osg-users mailing list

Reply via email to