At 8:45 AM -0400 8/19/05, Joseph Nastasi wrote:
Done and attached to this report:
http://www.realsoftware.com/feedback/viewreport.php?reportid=aefpnfic
Note that there are two issues. The intersect fails when it should
not the first time.
OK, we'll look into that (though I thought it was the opposite -- it
was claiming intersection when the bounds were actually far apart?).
The second issues is that the radius I assign using New
Bounds3D(New Vector3D, 63000) is changed when UpdateBounds is
called; setting to the value that was calculated when ComputeBounds
was used instead of New Bounds3D. So it seems that UpdateBounds
(whether called or when objects in question are rendered) does not
respect the assigned values.
Well, yes -- that's the whole point of UpdateBounds. It updates the
bounds to fit the object's current size, orientation, and position.
If you don't want it to update the bounds, then don't call that
method.
Best,
- Joe
--
Joe Strout REAL Software, Inc.
Vote for REALbasic (twice!) in the LinuxWorld Reader's Choice Awards:
http://linux.sys-con.com/general/readerschoice.htm
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|