At 10:40 AM -0700 9/21/05, Lo Saeteurn wrote:
Yes that is possible, but I would need to create something that
allows me to visibly see if there's a problem with the internal
method.
No, you should only need to see if it indicates an intersection, and
compare this with the correct answer (calculated by hand). Something
like:
Dim b as New Bounds3D
b.Center = New Vector3D(53,0.5,42)
b.Radius = 12.34
if b.LineSegmentIntersection( New Vector3D(50, 0.5, 42), _
New Vector3D(60, 0.5, 42) ) = nil then
MsgBox "See? It's broken!"
end if
Visibility and so on is just extra complexity -- which may be where
the real problem lies. That's why trying to isolate it to a
particular function will be so useful; you'll either demonstrate a
clear bug, or discover that the bug lies somewhere else.
At 11:38 AM -0700 9/21/05, Lo Saeteurn wrote:
So you see nothing wrong with the way I'm using it in my code?
I couldn't follow your code, at least in the time I had available to
look at it.
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>
|