Alexandre Julliard wrote:
> > You have to be careful here though. X assumes that image data is
> > allocated by malloc and will try to free it in XDestroyImage using
> > free. In principle we can free any image data ourselves (or define
> > our own DestroyImage function and hook it into the image function
> > pointers). We must then not use XGetImage but XGetSubImage instead.
>
> For X calls we can continue to use malloc, since it will be protected
> by the X11 section anyway.
Then my previous comment can be thrown in the bitbucket :-)
Greetings Bertho
