cairo/BUGS
Carl Worth 0fb5b1d4c4 Remove several entries in an effort to obsolete the BUGS file in favor of bugzilla and cairo/test. Specifically:
cairo_image_surface_create should clear image: NOTABUG. The user can clear if desired, and cairo clearing unconditionally would be performance overhead).
cairo_clip is really slow: FIXED/COVERED. Since the time this entry was added we've got rectangular, pixel-alignend clipping optimized. And there's a bug in bugzilla (https://bugs.freedesktop.org/show_bug.cgi?id=4191) for optimizing IN.
self-intersecting path is wrong: COVERED by test/self-intersecting.c.
Cairo is crashing Xnest: NEEDINFO. Is this still happening? Xfake has been working quite well for a very long time now.
font-size=0 in SVG does bad things: FIXED.
2005-08-22 16:56:43 +00:00

42 lines
1.2 KiB
Text

cairo-xlib-surface needs to do the Xlib register extension hack so
that it can listen for a Display close event. When it gets that, it
needs to run through its caches and eliminate anything associated with
that display.
--
The caches need to be invalidated at font destruction time.
--
Splines are not dashed.
--
The polygon tessellation routine has problems. It appears that the
following paper has the right answers:
http://cm.bell-labs.com/cm/cs/doc/93/2-27.ps.gz
[Hobby93c] John D. Hobby, Practical Segment Intersection with
Finite Precision Output, Computation Geometry Theory and
Applications, 13(4), 1999.
Recent improvements to make the intersection code more robust (using
128-bit arithmetic where needed), have exposed some of the weakness in
the current tessellation implementation. So, for now, filling some
polygons will cause "leaking" until we implement Hobby's algorithm.
--
cairo_show_text is not updating the current point by the string's advance values.
--
Caps are added only to the last subpath in a complex path.
--
ref_counts will go negative if destroy is called with ref_count ==
0. We noticed this in cairo_surface.c but it likely happens in several
places.