Hi J-S.

I'm afraid I don't have any suggestions, it'll require me to spend a
couple of hours investigating the issue, time that I don;t have right
now as I'm knee deep in tax returns and other pressing work.
Hopefully in the later half of next week things should start seeing a
little more sanity...

Robert.

On Jan 18, 2008 9:16 PM, Jean-Sebastien Guay
<[EMAIL PROTECTED]> wrote:
> Hello again,
>
> > local_x = 10  - local_y = 10
> > local_x = 1270  - local_y = 10
> > local_x = 1270  - local_y = 1014
> > local_x = 10  - local_y = 1014
> >
> > and indeed, if I run the same example with -2, I get the expected results.
>
> Trying something else, I modified the osgpick example (which uses a straight
> Viewer instead of CompositeViewer) to print the same info when clicking the
> mouse. I get, for example:
>
> local_x = 6.99997  - local_y = 1011
> local_x = 1268  - local_y = 1014
> local_x = 1264  - local_y = 24
> local_x = 17  - local_y = 24
>
> What's weird is that both times (osgcompositeviewer and osgpick), the view was
> set up with setUpViewAcrossAllScreens(). So it would seem that the behavior of
> getCameraContainingPosition() is different whether it's used through a Viewer
> or a CompositeViewer.
>
> I don't know the code itself, but shouldn't the behavior be the same?
>
> Modified osgpick example attached.
>
>
> J-S
> --
> ______________________________________________________
> Jean-Sebastien Guay     [EMAIL PROTECTED]
>                         http://whitestar02.webhop.org/
> _______________________________________________
> osg-users mailing list
> [email protected]
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
>
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to