On Tue, Nov 23, 1999 at 07:39:22AM +, Nick Lamb <[EMAIL PROTECTED]> wrote:
> rather than a missing feature, I wonder if all these tile-level probs
> are one thing or many???
The one who finds out should be forced to fix it ;)
Maybe we can find this before 1.2. And when these problems go away
On Tue, Nov 23, 1999 at 04:28:48AM +0100, Marc Lehmann wrote:
> It often ends up with gimp spinning in an endless loop or a segfault or
> corrupted images (including undo).
Eeek! This is definitely something wrong in the current implementation
rather than a missing feature, I wonder if all these
On Mon, Nov 22, 1999 at 06:45:15PM +, Nick Lamb <[EMAIL PROTECTED]> wrote:
> > one oepration (regardless of which) is being done at the same time. It gets
> > much worse when you do it on the same image.
>
> Are these "bad things" fatal?
It often ends up with gimp spinning in an endless loop
On Mon, Nov 22, 1999 at 02:49:50PM +0100, Marc Lehmann wrote:
> In current gimp you will notice lot's of bnad things happening when more then
> one oepration (regardless of which) is being done at the same time. It gets
> much worse when you do it on the same image.
Are these "bad things" fatal?
On Mon, Nov 22, 1999 at 01:18:17PM +0100, Michael Natterer <[EMAIL PROTECTED]>
wrote:
> Image map modifies the image in place and it's possible to do another
> operation while an image map tool dialog (e.g. threshold) is active.
In current gimp you will notice lot's of bnad things happening when
