On Aug 15, 2005, at 12:50 PM, Joseph J. Strout wrote:
Tiny, in comparison. But here's the odd thing. If I show the Bounds3D
in the debugger, Center(!), Minimum and Maximum are all NIL.
The debugger shows those? I wouldn't expect it to show them at all.
Have you tried logging them (e.g. to System.DebugLog)?
Yes, that's my next step!
Radius is 20.22 and the Type is correctly set to 2, which _means_ we
should be seeing Minimum and Maximum, not Radius (and center in all
cases).
No, it doesn't mean anything of the sort. The properties available
are always available, regardless of how you create the volume. If
it's a spherical volume, then Minimum and Maximum are computed to
enclose the sphere. If it's a box volume, then Center and Radius are
computed to enclose the box. You can create it either way, and
inspect it either way -- that's a feature.
Ah! I thought it was an either/or thing and the apparent lack of
visibility in the debugger reinforced that. It is nice and flexible
this way!
Assume they are okay. The Model is at 0,0,0 with a Radius of 20.22.
Planet.Position is at 0,-637989,0 and has a radius of 607813. Given
this, it doesn't seem like the Intersect should have returned True.
There should be 30156 of space between the two.
I agree. Can you reproduce this in a simple app -- create bounds1,
create bounds2, show that they intersect when they shouldn't?
I'll do that and open up a report if it truly is whacked.
Thanks!
--
Joseph Nastasi
Pyramid Design - a software development firm
http://www.pyramiddesign.us
Voice 609 601-0814 Fax 609 601-0815
Products:
A-OK! Spacecraft Simulation System - http://aok.pyramiddesign.us
A-OK! The Wings of Mercury
FTP Suite for REALbasic - http://ftpsuite.pyramiddesign.us
Proud Sponsors of REALbasic Olympics 2005
_______________________________________________
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>
|