BUGS

Section: Misc. Reference Manual Pages (and)
Updated: LIMITATIONS
Index Return to Main Contents

 6 "IRIT Version 6.0"   

NAME

BUGS and LIMITATIONS

Like any program of more than one line, it is far from being perfect. Some limitations, as well as simplifications, are laid out below.

* If the intersection curve of two objects falls exactly on polygon boundaries, for all polygons, the system will scream that the two objects do not intersect at all. Try to move one by EPSILON into the other. I probably should fix this one - it is supposed to be relatively easy.

* Avoid degenerate intersections that result with a point or a line. They will probably cause wrong propagation of the inner and outer part of one object relative to the other. Always extend your object beyond the other object.

* If two objects have no intersection in their boundary, IRIT assumes they are disjoint: a union simply combines them, and the other Boolean operators return a NULL object. One should find a FAST way (3D Jordan theorem) to find the relation between the two (A in B, B in A, A disjoint B) and according to that, make a decision.

* Since the boolean sum implementation constructs ruled surfaces with uniform speed, it might return a somewhat incorrect answer, given non-uniform input curves.

* The parser is out of hand and is difficult to maintain. There are several memory leaks there that one should fix.

* The X11 driver has no menu support (any easy way to have menus using Xlib!?).

* IBM R6000 fails to run the drivers in -s- mode.

* Rayshade complains a lot about degenerate polygons on irit2ray output. To alleviate the problem, change the 'equal' macro in common.h in libcommon of rayshade from EPSILON (1e-5) to 1e-7 or even lower.

* On the motif-based drivers (xmtdrvs etc.) clicking the mouse left and right of the scale's button produces stepped transformations. This step size is constant, and is not proportional to the distance between the mouse's position and the position of the button. The reason for the flaw is incorrect callback information returned from the scale in repeattive mode.

* Binary data files are not documented, nor will they be. They might change in the future and are in fact machine dependend. Hence, one platform might fail to read the other's binary data file.


 

Index

NAME

This document was created by man2html, using the manual pages.
Time: 07:28:34 GMT, July 20, 2024