Please provide a minimal, compilable example of your problem. Check it with a recent Qt6 version and if the issue still exists, create a bug report (or post it here and I'll take a look on it).

The check in setColor() is not needed - if there is an oom the app will crash.

@hellotiger Run glmark2-es2-drm and glmark2-es2-wayland on the arm board to check that the gpu runs normally, and the display is normal.

@astoffregen said in QT5 on Ubuntu 22.04 on arm64 missing modules:

I tried to install the libs via apt install, but I always get the info that they are already installed in never version.

Please show what you tried and what error message you get.
When you installed a new version of Qt5 then you should sync all packages to the same version.

@praveen_03 The code you have shared is correct. PErhapos it would be good to see the QML part, too ;-)

@crueegg
Hi, unfortunately, we had to cope with the same issue. The only way to circumvent it was to create a singleton class that handles a mapping between the id of the QMetaType and the custom alias.
See https://gitlab.inria.fr/dtk/dtk-core/-/issues/30 for more details.
Thib.

@kshegunov I have ~80 classes, each with 5-10 different properties (enums, POD, custom types, containers). The problem are all implicit (in a loop) conversions of these properties.

@ZaidX said in Visualize Realtime pointclouds on QT widget:

I dont understand what do you mean by "if its pure qt without any hardware accleration" .

With this I mean that you derive from QWidget and implement paint() using QPainter. This is comparatively slower than OpenGL or Vulkan. For these you need a QOpenGLWidget or QVulkanWindow. This then allows to use OpenGL or Vulkan directly for drawing while still using Qt for everything else (including mouse handling).

@ZaidX said in Visualize Realtime pointclouds on QT widget:

Bandwith: 3.55MB/s
Frequency: 4.9Hz

This sounds doable. Though it doesn't mean it is easy to reach interactive speeds.

@artem1997262 said in QMYSQL driver not loaded on Ubuntu:

Although below shows found that file

Where is it located?
And did you check whether it is 64bit this time?

Well I feel a bit silly, but I thought I had tried that. Seems to work now though.

Hi,

Not knowing the FreeBase API it's hard to answer. Do you have a link of it ?

In any case, the worst case scenario would be to fetch the whole data, change the fields you want and then send again the whole data.

@Christian-Ehrlicher thank you for your help :)

@FPEY said in QSortFilterProxyModel: Reset model shows ghost items:

EDIT: Nevermind, my issue was also a stupid mistake: I was simply not calling the function to make the whole reset model stuff when I had multiple lines selected ^^

Glad to hear that you managed to resolve your issue :)

I'm not exactly sure where the problem I was facing originated from hence I didn't leave any details as I don't want people to be mislead.
This was my first time working with QStandardItemModel. So far I have always implemented models directly by deriving from QAbstractItemModel.

When using the QStandardItemModel with the proxy model, the proxy's state was not invalidated when rows were inserted or removed (again, I don't know (yet) why).

The quick fix without actually understanding the problem was to invoke the QStandardItemModel::invalidate slot whenever rows were either inserted or removed:

connect(m_model, &model::rowsInserted, m_proxy_model, &QSortFilterProxyModel::invalidate); connect(m_model, &model::rowsRemoved, m_proxy_model, &QSortFilterProxyModel::invalidate);

Where:

m_model is of type QStandardItemModel* m_proxy_model is of type QSortFilterProxyModel*

It looks like a warning rather than an error per se.

You might have to configure something on the X server side.

I took a look with the ListDLLs tool but couldn't actually find the plugin being used by the 32-bit version, maybe some other DLL is handling that? Anyway, my problem is now solved so I'll mark this topic as solved.