From a681bf5c6a094d44824bb173ad555e671e1b540a Mon Sep 17 00:00:00 2001
From: ManoloFLTK <41016272+ManoloFLTK@users.noreply.github.com>
Date: Wed, 25 Mar 2026 11:13:46 +0100
Subject: [PATCH] Documentation change related to "RGB sub image drawing slow
 with larger images" (#1384)

---
 FL/Fl_Image.H | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/FL/Fl_Image.H b/FL/Fl_Image.H
index 8b8b433e8..7c6336542 100644
--- a/FL/Fl_Image.H
+++ b/FL/Fl_Image.H
@@ -287,9 +287,14 @@ public:
    (upper-left corner) of the image offset by the \c cx
    and \c cy arguments.
 
-   In other words:  <tt>fl_push_clip(X,Y,W,H)</tt> is applied,
-   the image is drawn with its upper-left corner at <tt>X-cx,Y-cy</tt> and its own width and height,
-   <tt>fl_pop_clip</tt><tt>()</tt> is applied.
+   Another way to see what part of the image gets drawn and where, is to consider this alternative writing producing the same output:
+   \verbatim
+   fl_push_clip(X,Y,W,H);
+   this->draw(X - cx, Y - cy);
+   fl_pop_clip();
+   \endverbatim
+   Repeated calls to this member function with the same image but varying <tt>W, H, cx</tt>, or <tt>cy</tt> arguments
+   may be more efficiently processed using the above alternative writing.
    */
   virtual void draw(int X, int Y, int W, int H, int cx=0, int cy=0); // platform dependent
   /**