Amazing stuff @slidinghotdog

A handy trick that you can use for future is:

You could use this.setProperty (which is a method in QObject) to set properties.
this way you wont need to implement many methods in the C++ wrapper.

For example:

and
To know what the properties are:
https://doc.qt.io/qt-5/qcombobox.html#properties

So you could just call this.property("propertyname", propertyvalue) and that should do. This will save some time :)

Thanks for the PR. Merging this.

Nice, i'll try that next time, looks like i can also use property() getter if the return value is a simple value or an implemented class right?

Yes that is correct.

@master-atul i'm trying to use this.property() but it returns QVariant and QVariant.toBool() returns a string, is that correct?

Hey @slidinghotdog
this.property('some property') would always return QVariant.
And with QVariant you can convert it to primitives like boolean, string, number, etc via

• variant.toBool() - converts to boolean
• variant.toString() - converts to string, etc

But also sometimes you need to get back complex objects like QRect, QPixmap, etc,, For these you would need to use the respective static methods like this.

const rect = QRect.fromQVariant(variant);
or

const pixmap = QPixmap.fromQVariant(variant);

etc.

@master-atul i was referring to the TS types here:

    toInt(): string {
        return this.native.toInt();
    }
    toDouble(): string {
        return this.native.toDouble();
    }
    toBool(): string {
        return this.native.toBool();

shouldn't they be changed?

@slidinghotdog Thats definetly a mistake 🙈 Thanks for pointing out!
The js values that we get are correct. But typescript annotations are wrong

Fixed in #255