Re: [osg-users] CompositeViewer regression between OSG 3.1.4 and 3.2

Hi Glenn, On 27 June 2014 22:08, Glenn Waldron gwald...@gmail.com wrote: Sure. These were the breaks: I see that you are testing 3.3.2 rather than 3.2.1. Both have the fix to the CompositeViewer event focus bug that you reported. 1) osg::Geode::DrawableList type is gone; replaced usage of

Re: [osg-users] CompositeViewer regression between OSG 3.1.4 and 3.2

HI Glenn et. al, I have been looking into the CompositeVIew/View focus issue and have resolved it by adding a render order sort into list of Cameras that have Viewport that enclose the current mouse position. The last Camera rendered will be the topmost one so can be taken as the one that gets

Re: [osg-users] CompositeViewer regression between OSG 3.1.4 and 3.2

Robert, I was in the process of building against OSG 3.3.2 to test, but ran into issues (osgEath doesn't build against it so I need to address that). I may not be able to complete testing until later since I'm heading off on vacation. Just wanted to let you know why I had not responded. Glenn

Re: [osg-users] CompositeViewer regression between OSG 3.1.4 and 3.2

Hi Glenn, Could you or Jason post the build breaks so I know where we stand w.r.t mods to Osg or osgEath to keep things building. Robert. On 27 Jun 2014 20:52, Glenn Waldron gwald...@gmail.com wrote: Robert, I was in the process of building against OSG 3.3.2 to test, but ran into issues

Re: [osg-users] CompositeViewer regression between OSG 3.1.4 and 3.2

Sure. These were the breaks: 1) osg::Geode::DrawableList type is gone; replaced usage of iterators with getNumDrawables + getDrawable(i) (tag 3.3.2) 2) osg::Drawable::getBound() renamed to getBoundingBox(). Replaced with a polyfill function (tag 3.3.2) Also computeBound() is now

Re: [osg-users] CompositeViewer regression between OSG 3.1.4 and 3.2

HI Remo, On 15 May 2014 14:48, Remo Eichenberger osgfo...@tevs.eu wrote: Any news on this? I've tried to fix it, but it is really complicated. I haven't had an opportunity to look at yet. Had lots of other work to tackle. Robert. ___ osg-users

Re: [osg-users] CompositeViewer regression between OSG 3.1.4 and 3.2

Robert, Any news on this? I've tried to fix it, but it is really complicated. Cheers, Remo -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=59444#59444 ___ osg-users mailing list

Re: [osg-users] CompositeViewer regression between OSG 3.1.4 and 3.2

Hi Remo, On 7 March 2014 07:30, Remo Eichenberger osgfo...@tevs.eu wrote: I also run into this issue. Does anyone has found a solution for it? I haven't had a chance to look deeply into the issue yet. Robert. ___ osg-users mailing list

Re: [osg-users] CompositeViewer regression between OSG 3.1.4 and 3.2

Hi Robert, I also run into this issue. Does anyone has found a solution for it? Thanks Remo -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=58511#58511 ___ osg-users mailing list

Re: [osg-users] CompositeViewer regression between OSG 3.1.4 and 3.2

HI Glen, Thanks for the example, I've tested it and can reproduce the problem - mouse movement+buttons events are captured by only the main view, while the wheel is captured by the inset view. For now I don't have a clue why it's happening, for sure it's a bug. The fact that the mouse wheel is

Re: [osg-users] CompositeViewer regression between OSG 3.1.4 and 3.2

Here is a minimal program that demonstrates the issue. OSG 3.2: the mouse scroll wheel works in the inset view; all other mouse events pass through to the underlying view. OSG 3.1.4: works as expected. #include osgViewer/CompositeViewer #include osgDB/ReadFile int main(int argc, char** argv)

[osg-users] CompositeViewer regression between OSG 3.1.4 and 3.2

Hi folks, I have an app that uses a CompositeViewer with one Master View that fills the window and multiple inset Views that sit on top of the main View. All Views share the same scene graph, but you can manipulate each one separately. In OSG 3.1.4 this worked, but after upgrading the OSG 3.2,