[cairo] CAIRO_STATUS_NO_MEMORY when passing incorrect scaling

[Travis Griggs]

On Jan 1, 2009, at 7:21 AM, Behdad Esfahbod wrote:

>>
>> What puzzled me in trying to track this down, is that the surface's
>> error state was CAIRO_STATUS_NO_MEMORY (at least,
>> cairo_status_to_string() reported no memory).
>
> That sounds wrong.  You shouldn't get an error on the surface at all.
> Should get it on the context.

Peter didn't say what platform he was running on. If he was running on  
either Windows or OSX, many of the "backend" errors there are cast as  
"no_memory" errors.

--
Travis Griggs
Objologist
I patented thinking... and I still can't find anyone infringing.