Bug 10141

Summary: Cairo-Nquartz in 1.3.14 fails many tests, and doesn't work correctly in demo program
Product: cairo Reporter: Hugo Vincent <hugo.vincent>
Component: quartz backendAssignee: Carl Worth <cworth>
Status: RESOLVED DUPLICATE QA Contact: cairo-bugs mailing list <cairo-bugs>
Severity: normal    
Priority: medium CC: hugo.vincent
Version: 1.3.14   
Hardware: x86 (IA32)   
OS: Mac OS X (All)   
Whiteboard:
i915 platform: i915 features:

Description Hugo Vincent 2007-03-01 02:27:47 UTC
Test transcript here: http://hugovincent.com/files/cairo-1.3.14-test.txt

Let me know what other information you need. 

Also, I tried the Cairo quartz demo from http://webcvs.cairographics.org/cairo-demo/quartz/ and it mostly works (draws the face of the clock correctly, doesn't render the hands at all...), but on the other hand, this demo hasn't been updated in almost two years.

In a simple test application I created, Cairo-NQuartz on a CGContext obtained from a Cocoa NSView does not render correctly (only renders some strokes/fills). Let me know if you want me to post the code and/or screen shots of the problem.
Comment 1 Hugo Vincent 2007-03-01 16:20:09 UTC
(In reply to comment #0)
> In a simple test application I created, Cairo-NQuartz on a CGContext obtained
> from a Cocoa NSView does not render correctly (only renders some
> strokes/fills). Let me know if you want me to post the code and/or screen shots
> of the problem.

Well, I've narrowed the problem down at least in the case of my test app, and the cairo-demo fdclock app to be a duplicate of bug 10036. (I was running snippets from  http://cairographics.org/samples/, where "user space" is normalised to a unit square, and line widths of around 0.04 are used. Changing the line widths to 1.0-2.0 makes the lines show up.)

Comment 2 Hugo Vincent 2007-03-16 18:36:37 UTC

*** This bug has been marked as a duplicate of bug 10036 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.