At 7:30 AM -0400 8/15/05, Joseph Nastasi wrote:
If I do the following:
Self.Planet.Bounds = New Bounds3D(New Vector3D,6078137)
The value 6,078,137 should be the tripping point for this:
If
Self.Model.Bounds.Intersects(Simulation.NaturalSystem.Planet.Bounds)
Then
Correct?
Well, something close to that, yes. That's a pretty big number, and
remember that these are stored internally in singles, not doubles.
Also, of course, it depends on how big Self.Model.Bounds is.
What happens is the if statement is satisfied when
Self.Model.Position.Y is at 6,391,141.
Well, how big is your model?
Also, there is a bug in 2005 (any version) where only the radius and
center are displayed in the debugger, regardless of Bounds Type.
http://www.realsoftware.com/feedback/viewreport.php?reportid=vxznzqii
I doubt that's a bug. I don't have the code in front of me, but the
debugger shows what properties are available; radius and center are
properties, and yes, they're available regardless of the bounds type.
The others are methods. (And yes, I realize that the docs may not
accurately reflect which ones are methods and which are properties --
it groups things conceptually rather than how they appear in the
debugger.)
Finally, Group3D does not calculate Bounds3D even though it is a
subclass of Object3D. It would make some types of bounds checking a
lot simpler if it was built in.
http://www.realsoftware.com/feedback/viewreport.php?reportid=wlknfiss
Agreed.
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>
|