-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error with computeBounds functions in the Cookbook's examples and OSG's current master branch. #13
Comments
Thanks Ardi. This is because the latest OSG trunk redefines Drawable as a Node type so computeBound() returns a sphere bound by default, as well as a new computeBoundBox() method for precise use. We need to update the recipes to fit this, but had better keep some backward compatibility for older versions, maybe using the OSG_VERSION_GREATER macro. It would be much appreciated if you could make a pull request, as I'm busy with some client work now. :-) |
Hi! I'll send you the pull request next week! :D Cheers! PS: It's Adri, not Ardi ;) On 24 October 2014 03:39, Rui Wang notifications@github.com wrote:
|
…since 3.21 release, due to Drawable inheriting now directly from Node.
Hello, I have the same problem as you. Can you tell me how to solve it? I don't know where to use OSG_ VERSION_ Greeter macro, thank you |
This is my compile error message In file included from /home/dzx/sonar_simulation/gui/osg_ocean/include/osgOcean/FFTOceanSurfaceVBO:21:0, |
In
NurbsSurface
andCloudBlock
, the functioncomputeBound
is redefined. But with the current OSG's master brach, the build process ends in an error:It seems that now
Drawable
has two functions for computing the bounds. The oldcomputeBound
now returns aBoundingSphere
, whereas the one returning aBoundingBox
is now namedcomputeBoundingBox
. Even though master isn't a stable release, I think the changes will remain for future releases.Modifying the source code for NurbsSurface and changing
computeBound
tocomputeBoundingBox
let me continue with the build.I can make a pull request with the changes if you want. :)
The text was updated successfully, but these errors were encountered: