[quote user="Xavi García Maranges"] that a distance of 0.1mm must be considered 0 for microstation ???[/quote]
Not for MicroStation. MicroStation is not involved in such evaluation! MicroStation can be treated as "element storage" and it's defined that element coordinates (like in other CAD systems) are stored as floating decimal point numbers accordingly to IEEE standard. It's completely your responsibility to define what precision is critical for you (but it cannot be better than precision ensured by the storage itself). Every tool in MicroStation does the same: It works based on the precision specification ... e.g. element placemetn is not critical, but 3D modeling using Parasolid require some extra precision settings.
[quote user="Xavi García Maranges"] I supose that a value of a exponent -10 or -12 is considered like a 0 , but a -4[/quote]
Again, it's you responsibility to research precision condition. Don't suppose, do serious math evaluation: What are your coordinates (in floating point math numbers close to zero have higher precision than big values numbers), what is required precision, with what precision you API works...
[quote user="Xavi García Maranges"] I must understand that I will not obtain a better precision of the connection [/quote]
What is better precision? It sounds to me like magic things or nonsense form math point of view:
- If there is line endpoint, I can probably easily make assignment like end-point-line-A = end-point-line-B, because it's only about to copy values from one structure to another.
- But if there is any more complex element (arc, curve...), the coordinates are "not free" because of element constrains ... arc and circle has to have the same distance from center point, curve is calculated somehow, so it's not possible to do simple "structure copy" line-endpoint to curve-endpoint.
- Any coordinate based on calculation like snap to curve, project to element etc. is always calcualted with limited precision.
At the end, to work with B-splines required pretty good konwledge of B-splines math itself and also at least basics of precision concept in path extended by floating point implementation issues knowledge (and VBA limitations knowledge in this case also). And maybe it's the reson why so many software (GIS / topology / analysis, modeling and visualization etc.) work with linear geometry only.
Regards,
Jan