Hi,
On Fri, 2007-07-20 at 12:29 +0300, Aurimas Juška wrote:
> I used to add GimpProgressbar in order to stop showing progress of
> temporary processing in image window (it was just created to capture
> progress events but not shown). Removing it seems to make the problem
> disappear. Is there any
> > Do other plug-ins show the same behavior for you? This sounds like a bug
> > in your plug-in. Is there perhaps an idle handler or a timeout still
> > running?
>
I used to add GimpProgressbar in order to stop showing progress of
temporary processing in image window (it was just created to captu
On 7/16/07, Sven Neumann <[EMAIL PROTECTED]> wrote:
> On Fri, 2007-07-13 at 14:50 +0300, Aurimas Juška wrote:
> > While testing my plug-in I noticed, that after quiting the plug-in The
> > Gimp *usually* (but sometimes not, not depending on what you do)
> > prints something like that: plug_in_flush
Hi,
On Fri, 2007-07-13 at 14:50 +0300, Aurimas Juška wrote:
> While testing my plug-in I noticed, that after quiting the plug-in The
> Gimp *usually* (but sometimes not, not depending on what you do)
> prints something like that: plug_in_flush(): broken pipe. It seems The
> Gimp wants to communica
While testing my plug-in I noticed, that after quiting the plug-in The
Gimp *usually* (but sometimes not, not depending on what you do)
prints something like that: plug_in_flush(): broken pipe. It seems The
Gimp wants to communicate with the plug-in after it's process has
terminated. I added g_usle
