[Heini]

Hi,

setting the SingleSpriteFromFile´s mirrorX property, results in an error message: “Cannot assign to non-existent property”. But the documentation says, the property exists: http://felgo.com/doc/vplay1-singlespritefromfile/

 

Cheers

Heini

[Heini]

Ok, after updating to the latest daily builds, mirrorX is working, but the whole game is looking quite different now o_O. The following code for example does not work anymore:

      Row {
             Repeater {
                 model: 10

                 SingleSpriteFromFile{
                     filename: "spriteSheets/spriteSheet1-sd.json"
                     source: "image.png"
                     height: 40
                     width: 40
                     y: 280
                 }
             }
         }

 

It seems also, that there is a change with the quality of png images, where the edges are not rendered much accurate any more and are quite frayed now. I am using ParallaxItem with an Image inside. This image (png) is getting rendered with a black border now.

Hoping for help,

Heini

• This reply was modified 10 years, 2 months ago by  Christian.

[ChristianFelgo Team]

Hi Heini,

the rendering code did not change between the version changes – are you sure it is related to that?

From what I see in your example code, you are drawing 10 images on top of each other which might lead to the border issues. Can you post a simple image which shows your issue and the accompanying demo code?

Cheers, Chris

[Heini]

Hi Christian,

to avoid any confusion – i am telling about 2 different issues, both resulting from updating to the latest daily builds.

 

1) The code posted above, worked with the latest stable build, but fails with daily. However, after setting the x property manually its working now also with daily builds.

 

2) It seems that the Clipping Element is causing a rendering error now, when it is containing png images with “soft” edges (i.e. image shape fades out with a gradient). In this case the images will be rendered with an ugly black border. Also setting Flickable.clip: true, results in the same effect.

 

Cheers,

Heini

[ChristianFelgo Team]

Hi Heini,

so the first issue is “kind-of” solved?

Regarding your 2nd issue: could you post a complete sample project (ideally in a single QML file) which shows this error so we can reproduce it?

Cheers, Chris

[Heini]

Hi Chris,

 

yes, I´ve found a working solution for the first issue.

 

To reproduce the second issue, please try the following code:

import VPlay 1.0
import QtQuick 1.1

GameWindow {
    activeScene: scene

    width: 960
    height: 640

    Scene {
        id: scene
        width: 480
        height: 320

        Clipping{
            id: clipping
            anchors.fill: parent

            Flickable{
                id: flickable
                anchors.fill: parent
                contentHeight: background.height
                contentWidth: background.width
                flickableDirection: Flickable.HorizontalAndVerticalFlick
                //clip: true //setting to true will have the same effect, even without using a Clipping

                Rectangle{
                    id: background
                    color: "white"
                    width: 1000
                    height: 1000
                }

                Image {
                    id: backgroundImage
                    width: 1000
                    fillMode: Image.PreserveAspectFit
                    source: "image.png"
                    y: 500
                  }

            }//end Flickable
        }//end Clipping

    }
}

I used this image for the example: http://www.directupload.net/file/d/3535/rgomymyl_png.htm

Here is a screenshot of the result when using the latest stable build: http://www.directupload.net/file/d/3535/t3kpgzfk_jpg.htm

And here is the result when using actual daily builds: http://www.directupload.net/file/d/3535/7ytsv63n_jpg.htm

 

Cheers,
Heini

• This reply was modified 10 years, 2 months ago by  Guybrush.

[ChristianFelgo Team]

Hi Heini,

thanks for your code and your screenshots! These will help us to find the issue.

We’ll let you know as soon as we have news about this issue.

Cheers, Chris

[AlexFelgo Team]

Hi Heini,

what “latest stable build” have you been referring too? I tried it with 1.5 and also ran into the issue.

Cheers,
Alex

[AlexFelgo Team]

Never mind, I just found the cause of this issue we will add the fix to the next daily build.

Thank you very much again for your help!

Cheers,
Alex