File tree Expand file tree Collapse file tree 2 files changed +5
-4
lines changed Expand file tree Collapse file tree 2 files changed +5
-4
lines changed Original file line number Diff line number Diff line change 59
59
* libvips operations are all functional: they take zero or more existing input
60
60
* images and generate zero or more new output images. Images are
61
61
* never altered, you always create new images. This means libvips can cache
62
- * and thread very agressively .
62
+ * and thread very aggressively .
63
63
*
64
64
* The downside is that creating entirely fresh images each time can be very
65
65
* slow. libvips has a range of tricks to avoid these problems, but there are
68
68
* need to draw 1,000 straight lines, a 1,000 operation-deep pipeline is going
69
69
* to be a slow way to do it. This is where the draw operations come in.
70
70
*
71
- * To use these operations, use vips_copy () to make a copy of the image you
72
- * want to modify to ensure that no one else is using it , then call a
71
+ * To use these operations, use vips_image_copy_memory () to make a private
72
+ * memory copy of the image you want to modify , then call a
73
73
* series of draw operations.
74
+ *
74
75
* Once you are done drawing, return to normal use of vips operations. Any time
75
76
* you want to start drawing again, you'll need to copy again.
76
77
*/
Original file line number Diff line number Diff line change @@ -3318,7 +3318,7 @@ vips_image_rewind_output( VipsImage *image )
3318
3318
* Call this before using the draw operations to make sure you have a
3319
3319
* memory image that can be modified.
3320
3320
*
3321
- * vips_image_copy () adds a null "copy" node to a pipeline. Use that
3321
+ * vips_copy () adds a null "copy" node to a pipeline. Use that
3322
3322
* instead if you want to change metadata and not pixels.
3323
3323
*
3324
3324
* This operation is thread-safe, unlike vips_image_wio_input().
You can’t perform that action at this time.
0 commit comments