UpdateRects: bug in X11 driver?

SDL Development
1

While we’re on a bug roundup, I’ve always noticed with SDL that if you call
UpdateRects with a rectangle that’s outside the bounds of the surface you’re
updating to, you get an Xlib error like so (e.g. on an 800x600 screen) :

Updating rect 396,494,188,187
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 147 (MIT-SHM)
Minor opcode of failed request: 3 (X_ShmPutImage)
Value in failed request: 0xbb
Serial number of failed request: 16
Current serial number in output stream: 17

Should UpdateRects perform this kind of clipping itself, or is this
deliberately the caller’s responsibility? So far I’ve always been careful but
I wonder whether this shouldn’t happen automatically.–
Matthew > http://www.soup-kitchen.net/
> ICQ 19482073

2

Matthew Bloch wrote:

While we’re on a bug roundup, I’ve always noticed with SDL that if you call
UpdateRects with a rectangle that’s outside the bounds of the surface you’re
updating to, you get an Xlib error

…

Should UpdateRects perform this kind of clipping itself, or is this
deliberately the caller’s responsibility?

The latter, I think. The documentation says, “The rectangles must all
be confined within the screen boundaries (no clipping is done).”

Torbj?rn Andersson