On Aug 19, 2005, at 11:41 AM, Joseph J. Strout wrote:
Really, I should be able to set a radius that is smaller than the
actual geometry and have Intersect respect and use that.
Right?
Yes, and so you can. Just don't let it be Updated (which does mean,
you'll have to store this somewhere other than the Object3D.Bounds
property).
Okay, so then I would have a separate bounds3D and use the Intersect
test with that Bounds3D and not the one linked with the Object3D.
So, while I haven't looked at your report yet, I'm starting to think
perhaps there is no bug here. Is it that you're trying to use a
bounds much smaller than the actual geometry, but the auto-updating is
expanding this to fit the actual geometry, which is then causing the
intersection to report true?
Yes, I think that is exactly what's happening. I totally forgot the
connection between Object3D and it's Bound property would force the
update and thereby change the radius. I'll double-check and kill the
report.
Thanks!
Joe
--
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>
|