[Martin]

Hey,

we are currently trying to port our code to Felgo 2 and it seems that PolygonItem is not supported yet. Are there any plans or alternatives for this? Advise is greatly appreciated since our level construction relies on it. Could you add it in one of the upcoming releases?

Cheers Martin

[ChristianFelgo Team]

Hi Martin,

thanks for your upvote for PloygonItem! We will add it to the upcoming release..

Cheers, Chris

[ChristianFelgo Team]

Do you also need the texture property or only the drawing part?

More specifically, which of the PolyognItem properties are you using at the moment?

Cheers, Chris

[Martin]

Hey Chris,

We use color filled polygons, no textures.

Cheers, Martin

[Paweł]

Hi,

is there any chance to use texture or clip properties already?

I’m trying to create an item which can be cut into pieces.

[GüntherFelgo Team]

Hi Pawel!

Yes, you can use the texture property already to fill the specified polygon with a texture (which is clipped to fit the polygon and repeated in x,y dimensions if necessary). Another way to achieve a similar effect would be to use an OpacityMask to hide certain areas of an Item. (maybe this solutions works better for your idea).

Best,
Günther

[Paweł]

The problem is I cannot see the texture property.

import Felgo 3.0
import QtQuick 2.0

...

Scene {
	
	...

	PolygonItem {
		id: polygon

		anchors.centerIn: logo
		vertices: [
			Qt.point(0, 0),
			Qt.point(100, 0),
			Qt.point(50, 100)
		]

		//texture: "../../assets/img/splash/logo.png" //not visible
	}
}

QtCreator says “Invalid property name”. I am using the VPlayBase Plugin v1.0.13.

However OpacityMask works just fine. Thanks! 🙂

[GüntherFelgo Team]

No problem!

It’s true that we missed to add the property to the auto-completion, I corrected that just now and it should work for the next update.

Anyhow, the property should be usable even without auto-completion. I tried the texture-feature in a demo project myself and had no problems. Also, the PolygonItem is unrelated to any plugins – maybe your error came from somewhere else?

Best,
Günther

 

[Paweł]

I’ve tried it now and it works fine. Probably my bad. Thank you again 🙂

Btw. I’ve noticed that there is the same auto-completion issue with localAxisA from PrismaticJoint. However it worked like a charm for the first time 😉

[GüntherFelgo Team]

Cool – thanks for helping to solve these auto-completion problems 😀