Leon Matthes

Hi, thank you for the feedback, it's super valuable, sorry this was such a painful experience for you. Regarding the issues with the book; we're up for a new release...

That's just a shared CXX type, so might be a CXX issue. :thinking: Can you try reproducing with just a CXX Bridge and a shared type?

@CarlSchwan good to see this change progressing nicely :+1: Quick chime-in on the `#[qproperty(get=Self::x)]` API. I've just noticed that the `Self::` part might be redundant, or even misleading in the...

> I don't think there is a way to specify a getter/setter that is not on the `qobject::MyObject` and I don't think this would make sense. Regarding the syntax, I...

Superseded by #994

I think it's best to opt for a `--cfg` option. The issue with Cargo features is that they're additive, so if any of your transitive dependencies enables it, it's enabled...

> > beginInsertRows and endInsertRows should probably be unsafe to call directly, as calling one without the other is undefined behavior, aka. unsafe. > > Is that really undefined behavior...

@ahayzen-kdab I get this error on Fedora as well: ``` warning: Could not open /usr/lib64/libQt6Qml.prl file to read libraries to link: No such file or directory (os error 2) warning:...

We'd also have to wrap the `tr` call and friends, right? Also, how would Qt find all the strings to be translated? :thinking: Or should we rely on Rust-native translations...

Side note whilst skimming this: It seems this brings up the issue of how stable the binary representation of certain Qt classes is (i.e. QPoint). We should really figure this...