Clemens Eisserer wrote:
> > Pixmaps are reference-counted and the picture takes a reference on the
> > pixmap, so the pixmap can't go away before the picture.
> >
> > However this isn't true for windows, so as soon as the window is
> > destroyed presumably the picture is destroyed as well or beco
Hi Michel,
> Pixmaps are reference-counted and the picture takes a reference on the
> pixmap, so the pixmap can't go away before the picture.
>
> However this isn't true for windows, so as soon as the window is
> destroyed presumably the picture is destroyed as well or becomes
> invalid.
Can this
On Fre, 2010-08-27 at 21:43 +0200, Clemens Eisserer wrote:
> Hi again,
>
> Seems I have found the cause of the problem: Freeing Pictures that
> belong to an already destroyed window cause the RenderBadPicture
> error. The XID values in the error-log were wrong and therefor
> misleading.
>
> What
Hi again,
Seems I have found the cause of the problem: Freeing Pictures that
belong to an already destroyed window cause the RenderBadPicture
error. The XID values in the error-log were wrong and therefor
misleading.
What puzzles me is the inconsistent behaviour:
When a Window is destroyed, all i
Hi,
I have some code which causes "RenderBadPicture" errors from time to
time, and I have troubles finding the cause.
I have inserted some debug code and switched to synchronous mode,
however I don't get an idea whats going wrong.
Some pictures don't seem to cause problem, whereas other pictures
