Re: Bug in pixbuf->copy ?

On Apr 17, 2006, at 9:27 AM, Jaap Karssenberg wrote:

It seems that the problem with the copy() function is not recursize (the copies of a copy are not the same) so this works for now.

It would help to see your code and hear your explanation of how you know the objects are not distinct copies. I tried a simple script and could not reproduce your results.

Gtk2::Gdk::Pixbuf::copy() has a trivial implementation that calls gdk_pixbuf_copy() and transfers ownership of the new pixbuf to the caller. gdk_pixbuf_copy()'s documentation claims that it returns either a new pixbuf or NULL, which is confirmed by a quick read of the source. The origin of the source pixbuf (how many references, is it already a copy of something) is never queried, and the actual data of the pixbuf is a real in-memory duplicate of the original, via g_try_malloc() and memcpy().

I don't have a drinking problem,
'cept when i can't get drink.
  -- Tom Waits

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]