diff options
author | Carl Worth <cworth@cworth.org> | 2005-08-24 08:46:02 +0000 |
---|---|---|
committer | Carl Worth <cworth@cworth.org> | 2005-08-24 08:46:02 +0000 |
commit | 2cd76fc77f5455fb2bb141a4e75b3ced0004a1e2 (patch) | |
tree | 6c9885fa9f1b6787508e0aa1d2351f74937a2ee9 /PORTING_GUIDE | |
parent | aa4b9f4b00c5cf7be0f525caa2419b00a0dc26b5 (diff) |
Update name from "0.5 porting guide" to "1.0 porting guide."
Diffstat (limited to 'PORTING_GUIDE')
-rw-r--r-- | PORTING_GUIDE | 14 |
1 files changed, 11 insertions, 3 deletions
diff --git a/PORTING_GUIDE b/PORTING_GUIDE index b8bdd37b..7488173c 100644 --- a/PORTING_GUIDE +++ b/PORTING_GUIDE @@ -1,9 +1,9 @@ ...-----=======-----... - Cairo 0.5 Porting Guide + Cairo 1.0 Porting Guide ...-----=======-----... Here are some notes on more easily porting cairo_code from cairo 0.4 -to cairo 0.5. It is sorted roughly in order of importance, (the items +to cairo 1.0. It is sorted roughly in order of importance, (the items near the top are expected to affect the most people). Automated API renamings @@ -224,11 +224,19 @@ Was: cairo_set_rgb_color (cr, 0., 0., 0.); cairo_rectangle (cr, 0., 0., surface_width, surface_height); cairo_fill (cr); + or: cairo_set_rgb_color (cr, 0., 0., 0.); + cairo_set_operator (cr, CAIRO_OPERATOR_CLEAR); + cairo_rectangle (cr, 0., 0., surface_width, surface_height); + cairo_fill (cr); + Now: cairo_set_source_rgba (cr, 0., 0., 0., 0.); cairo_set_operator (cr, CAIRO_OPERATOR_SOURCE); cairo_paint (cr); -NOTE: Using cairo_rectanlgle and fill would still work just fine. It's + or: cairo_set_operator (cr, CAIRO_OPERATOR_CLEAR); + cairo_paint (cr); + +NOTE: Using cairo_rectangle and fill would still work just fine. It's just a lot more convenient to use cairo_paint now, (particularly as it doesn't require you to even know what the bounds of the target surface are). |