On Sun, 2004-03-07 at 12:53, bulia byak wrote:
Do you know any code saying "if something, do not draw the stroke"? Since the stroke disappears completely, this is likely to be such a "draw or not draw" switch. I know of one, which you introduced lately (the check for width > 0.01 in nr-arena-shape) and I tried to disable it but this did not help. Maybe there are others checks like that somewhere?
I highly doubt it's an "as coded" bug -- livarot doesn't do anything platform specific in this regard, so the code should behave identically on both platforms (on the same processor architecture).
Compiler and optimizer bugs aside, the most likely problem is that memory is being used uninitialized or after being freed.
I just ran valgrind on Inkscape, and found that livarot does indeed generate a _large_ number of warnings about data being used uninitialized.
If we can correct that, the renderer should behave predictably on all platforms.
-mental