Hi Robert, the comment/documentation is good. Using setDatabaseCacheReadCallback(0) to disable the paging seems better than introducing a new flag. Nevertheless it would be great ot have a simple to use flag in the static method. That would allow to calculate HAT still with only one line of code.
It seems we can't get an agreement about the HOT calculation within the HAT class, so what would be your recommendation to provide the following function with only one line of code (like HAT): HOT with paging HOT without paging. Creating a HeightOfTerrain class? Or should I rearrange the code that computeIntersection only computes the intersection points and the HAT and HOT computation is performed in the static functions seperately to avoid unneccessary computations? Or shouldn't HOT calculation be included into OSG? Of course I can integrate that HOT computation function in the utils of osgVisual, but I think it is usefull for more people in OSG. You are right, HOT can be calculated by the lineintesection classes, but for beginners it is a quite steep learning curve. a convenient function like your HAT calculationis more encouraging than 20 lines of intersection code. I'll be on vacation for 3.5 weeks in sourth america/peru in august *smile* Cheers, Torben ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=41439#41439 _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
