[Jan]

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

[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;
	}
}

 

[ChristianFelgo 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