Find the Best Demos and Examples

Check out this quick tour to find the best demos and examples for you, and to see how the Felgo SDK can help you to develop your next app or game!

Forums

OverviewFelgo 2 Support (Qt 5) › Scene: returning 1 for the xScaleForScene, but sceneGameWindow was invalid!

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #8414

    Jan

    Does anyone know how to get rid of this or how this can happen?

    #8415

    Jan

    Here is a boiled down snipped; basically its the mechanism from the flappybird demo(which does not throw that message). if I take out the assignment of visible and enabled, it works, but then I get other clashes with conflicting scenes in my project.

    import Felgo 3.0
    import QtQuick 2.0
    
    GameWindow {
    	id: window
    	width: 1024
    	height: 768
    
    	property alias window: window
    
    	Scene {
    		id:splash
    		width: 480
    		height: 320
    		opacity: 0
    	//////	// NOTE: in qt5, an opaque element is not invisible by default and would handle the mouse and keyboard input!
    	//////	// thus to disable also keyboard focus and mouse handling and make an item invisible, set visible and enabled property depending on opacity
    		visible: opacity === 0 ? false : true
    		enabled: visible
    	}
    
    	activeScene: splash;
    
    	// show the splash and start the loading process as soon as the GameWindow is ready
    	Component.onCompleted: {
    		splash.opacity=1;
    	}
    }
    

     

    #8417

    Christian
    Felgo Team

    Hi,

    you can safely ignore this debug output, everything is calculated correctly. In the next Felgo version, this debug output will be removed.

    Cheers, Chris

Viewing 3 posts - 1 through 3 (of 3 total)

RSS feed for this thread

You must be logged in to reply to this topic.