Re: [osg-users] context IDs

Hi Andy, It's quite a while since I worked specifically on the osg::State, ContextID, osg::GLExtensions management. In principle it should be possible to reuse ContextID's, the sticky issue of whether the GLExtensions object is recreated for each new graphics context is something I haven't person

Re: [osg-users] osgQt include files

Hi Michael, Thanks that help understanding the issue. CMake finds the include file named 'osg/Version' in /usr/local/include but fails to find any library for the following components 'osgDB', 'osgGA', 'osgUtil', 'osgText', 'osgViewer', 'osgWidget ' and lastly ''osg' not 'OpenThreads' itself. Fo

Re: [osg-users] context IDs

Thanks. The problem is in GLExtensions.cpp. It has some maps that it keeps, and it adds contexts and does not take them off. But GraphicsContext will provide an old, no-long-used context ID, and that ID can look up the wrong thing in GLExtensions.cpp if we have changed from hardware to softwa

Re: [osg-users] context IDs

OK, I've digested some more. I see what you mean (I think) about ~State clearing the GLExtensions object from the static map (s_extensions) defined in GLExtensions.cpp. However, if the next GLExceptions::Get will make a new one, the GLExtensions constructor will use other static maps: s_glExte

Re: [osg-users] context IDs

Hi Andy, I have just had a quick look at the various s_* containers in GLExtensions.cpp and I think these are an old hang over that should be removed and replaced by code that is embedded into the GLExtensions object so that it can be constructed and destructed. Short of this refactor perhaps the

Re: [osg-users] context IDs

Thanks, I'll take a look. I am hoping this will be more remove than replace, not needing multiple levels of caching. thanks andy -Original Message- From: osg-users On Behalf Of Robert Osfield Sent: Wednesday, September 19, 2018 2:28 PM To: OpenSceneGraph Users Subject: Re: [osg-users