Funny image layer memory

[Vadim Peretokin]

Here's my use case:

Imported an image, saw that it is too big and doesn't fit in the dimensions I want. I delete the layer, manipulate the image, import again - and something funny shows up. It's like a merge of my previous image that was there and the current one.

So I deleted the layer, tried again - same thing. Tried moving and renaming the image, but it's still the same. At this point I suspect that the layer isn't getting deleted properly or something - so I'll try using a new slide and moving things around.

At any rate, here is my project in its current state and the image. Just try adding a new image layer onto the 2nd slide and see that the image that appears is not what you actually imported.

[Vadim Peretokin (vperetokin)]

Hm, no, same thing on a new slide. I'll pause for now.

[Justin Clift (justinclift)]

Ouch, that sounds like a serious bug, and will definitely need to be addressed/fixed/etc before 0.8.0-alpha 6 release.

Thanks Vadim. :)

[Justin Clift (justinclift)]

Yep, there is definitely something strange going on here with the image. My first guess is that transparency in the image isn't being handled correctly. :(

Need your input: :)

  1. In the screenshot I'm attaching, the import.png image is loaded into Salasaga. There are coloured parts in the import.png image showing words like "multiline / AND trigger", "filter", "match all", "colourizer tr".

      Do these coloured parts exist in the source image on your system? (even if they've been made transparent)

Asking because loading the same image with The Gimp has these areas as transparent. Wanting to know if these coloured areas (as shown in the screenshot) are being transported from your system or being invented by mine. :)

  2. Which program was used to create the import.png image?

      Figuring it might be handy for me to have that program loaded as well while looking into this.

[Justin Clift (justinclift)]

Just noticed that when the project is exported to swf, the imported image looks ok.

Seems like the problem is with the code displaying the image in the working area wrongly.

[Vadim Peretokin (vperetokin)]

On Tue, Dec 8, 2009 at 6:18 AM, Justin Clift <email address hidden> wrote:

> Yep, there is definitely something strange going on here with the image.
> My first guess is that transparency in the image isn't being handled
> correctly. :(
>
> Need your input: :)
>
> 1. In the screenshot I'm attaching, the import.png image is loaded
> into Salasaga. There are coloured parts in the import.png image showing
> words like "multiline / AND trigger", "filter", "match all", "colourizer
> tr".
>

>
> Do these coloured parts exist in the source image on your system?
> (even if they've been made transparent)
>

No, I cut them out:
http://www.ubuntu-pics.de/bild/33514/screenshot_210_EWmKpm.png

> Asking because loading the same image with The Gimp has these areas as
> transparent. Wanting to know if these coloured areas (as shown in the
> screenshot) are being transported from your system or being invented by
> mine. :)
>
> 2. Which program was used to create the import.png image?
>

shutter and gimp in the end. gimp was used to cut out the bottom options

>
> Figuring it might be handy for me to have that program loaded as
> well while looking into this.
>
> --
> Funny image layer memory
> https://bugs.launchpad.net/bugs/493352
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Justin Clift (justinclift)]

This is taking more time to fix than expected, so is now being targeted for the release after 0.8.0-Alpha6 instead.