Leon Matthes

I'm trying this out right now. The problem currently seems to be the Classes.md file that lists all Classes, and all other listing files. They are accessed under the `Classes/`...

The output is indeed completely flat. The problem is a mix of the links doxybook2 generates, as well as the way they are handled by mkdocs. In the `Classes.md` file,...

Is there an option somewhere in mkdocs to translate the link output format to link to the .md files?

Hm, setting `linkSuffix` to `".md"` seems to fix the issue :thinking: So my current settings are: - `"linkSuffix": ".md"` - `"baseUrl": ""` - `"useFolders": false` Which seems to work well...

> To avoid collisions in QML we may need to allow for a custom name to be specified in the macro, eg `#[cxx_qt(QObject, qml_name = "MyObject")]` I don't think this...

Make sure typos don't end up creating weird compiler issues (i.e. someone typed `data` instead of `Data`).

Note: QRect's interface should propably *not* mimic Qt directly. set_x and set_y will change the width and height, which is not at all obvious/expected behavior. So we should improve on...

> We also need to consider how to avoid collisions on the Rust side eg for wrappers, a separate struct is possible but tricky as C++ would need to call...

We should also check for which types we can make the members public. QPoint comes to mind. I think in the data-driven design of Rust this might be more idiomatic.

Hm, it's an `example`, not a `test`, so probably best to fix this, unless someone tries to copy that code into their own CMake and have things break. Should just...