Re: inline pixbufs

[Federico Mena Quintero <federico helixcode com>]

Darin Adler <darin@eazel.com> writes:

> A problem with putting row stride in is this: There may be restrictions
> about which row strides can be efficiently supported on different platforms.
> If the code that reads the image uses the row stride stored in the flattened
> form without taking into account what's supported on the platform, you might
> get a slow-to-draw image (or perhaps even an unusable one?). So in the
> general case the reading code needs to select an appropriate row
> stride.

The gdk-pixbuf rendeing/scaling code needs to be able to handle any
rowstride.  Period.  If people happen to be using slow rowstrides, too
bad for them.

For the Bonobo case, you can transfer an image without padding (to
reduce size) and then gdk_pixbuf_copy() it on the other side so that
it will hopefully get an optimal rowstride.

  Federico