The indexify() method uses a hash table, so the two Objects would
have to have the same hashCode() to get the same index. The
Classes being used are the Vecmath classes Point3f, Color3f, etc.
Looking at the hashCode() implementation for those classes, there
is no tolerance - the two Objects' x, y, & z values must be exactly
equal.
-Paul
> Delivered-To: [EMAIL PROTECTED]
> X-Originating-IP: [203.199.228.2]
> Mime-Version: 1.0
> X-OriginalArrivalTime: 14 Jul 2001 20:40:22.0203 (UTC)
FILETIME=[33D838B0:01C10CA5]
> Date: Sat, 14 Jul 2001 20:40:21 -0000
> From: R Vegan <[EMAIL PROTECTED]>
> Subject: [JAVA3D] Ques. on GeometryInfo "indexifier"
> To: [EMAIL PROTECTED]
>
> Hi All ( and specifically to Paul Pantera )
>
> I gather from the GeometryInfo API that it can "indexify"
> unindexed geometry. What I would like to know is whether
> GeometryInfo uses any kind of tolerance to merge
> nearly coincident vertices ( for example, floats differing
> simply by round-offs ). If so, what is the value of
> this tolerance ?
>
> Thanks in advance
>
> Raj Vaidya
>
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff JAVA3D-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
