On Fri, Aug 16, 2024 at 8:07 AM Ulf Hermann wrote:
> You can indeed write your .qmltypes files manually and then pass
> NO_GENERATE_QMLTYPES to prevent them from getting generated. However,
> this is not for the faint of heart (hence the "NO" prefix).
>
OK. Assuming I'm reckless enough to try, w
David,
I’m was looking to use QQuick API instead of QWidgets.
Instead of a video it could be a shader, or an image. The idea is to have a
processing, on a certain input.
I also need to do this fast, very fast. Is Qt suitable for this?
Regards,
Nuno
> On 15 Aug 2024, at 21:55, David M. Cott
Jean,
I’ve been looking at the code.
Essentially you only use QRhiBuffer from Qt.
Do you think Qt does not provide the enough performance to handle this task or
is any architectural limitation from Qt scene graph that lead to this decision?
Thanks!
Regards,
Nuno
> On 15 Aug 2024, at 16:01,
You can indeed write your .qmltypes files manually and then pass
NO_GENERATE_QMLTYPES to prevent them from getting generated. However,
this is not for the faint of heart (hence the "NO" prefix).
You can probably also build the "A" library yourself, retrieve the
metatypes.json file from that, a
Thanks Ulf. But as moc figured out everything it knew about `A` by reading
`A.h`, and given that that header is still available, I would assume that
it could just repeat the process, even if now `A.h` was only the interface
to a "foreign" object...
But assuming I really don't get access to that inf
Unfortunately this is not enough in my real case, where `A` is not only
a different library, but is provided by a separate (debian) package,
so `A` in the current project is an INTERFACE target, which
`qt_extract_metatypes()` falls over with an obscure error.
Indeed without metatypes we cannot
