You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just want to thank you again for this amazing work. I was able to throw together a pretty substantial prototype in a very short amount of time.
I really feel like this is the best library hands down to write UIs in Rust.
As an aside, I am wondering if we can use the qmetaobject to get around limitations with the lack of inheritance in rust? Do you have plans for tackling this?
The text was updated successfully, but these errors were encountered:
I don't know how to emulate subclasses with QMetaObject. As far as I know, it only manages signals, slots, properties, and invokable methods, so it doesn't even know about most virtual methods. And there are many classes in Qt that can be usefully subclassed but do not have a QMetaObject.
Supporting inheritance properly is definitely possible. See an old draft at rust-qt/ritual#26. I just don't have enough time to implement it right now, but hopefully I'll do it eventually.
I suppose that handling signals, slots, properties form a part of what one reaches for subclasses for in qt in c++. Certainly this doesn't cover everything, but i would imagine that one can get really far with composition + custom signals/slots/properties. Sure, no overriding virtual methods, etc. but still quite useful.
Just want to thank you again for this amazing work. I was able to throw together a pretty substantial prototype in a very short amount of time.
I really feel like this is the best library hands down to write UIs in Rust.
As an aside, I am wondering if we can use the qmetaobject to get around limitations with the lack of inheritance in rust? Do you have plans for tackling this?
The text was updated successfully, but these errors were encountered: