@Luuk00101 said in Can't set the icon on the Windows build:

Do you think the path resolves to an invalid one on when we run it on Windows?

This is the first thing I would check.

Resource files: https://doc.qt.io/qtforpython-6/overviews/resources.html

@deltax12 take a look at this stack overflow thread for hints on how do to it.

Solved, sorry to bother everyone.
I needed to designate my patient_id as UNIQUE

I found the problem.

The problem is that I update labels in show_gaze_information.

This function is a callback that is called when a message is published on the topic.

To correct the code, in function show_gaze_information, the message should be stored in a variable. Nothing should be modified in UI.

Then in main body of code, I added this part:

# update gaze infor periodically timer_gaze = QtCore.QTimer() timer_gaze.timeout.connect(update_gaze_information) timer_gaze.setInterval(500) timer_gaze.start()

This code periodically calls update_gaze_information every 0.5 seconds. Now, in this function, I update labels in the UI.

@VRonin Yeah you are right. Usually my custom widget has another widgets (like another label for text, button for submit etc.) so I used setItemWidget. But your way better for only images.

QScreen should also be available for PyQt.

@Pl45m4 no but I don't know how to do that sizeHint() can return the right size in a layout.and I have a valid parent.

In that case you could create a widget that comes on top your UI, make it transparent so you can see through it and then cut the holes you want when you need to follow the animation.

Because we had declarations of shortcuts littered all over the place we came up with the following solution to handle them in one place.

We derived a class MyApplication from QApplication and overrode bool notify(QObject *receiver, QEvent *e) override. Within this function we checked e->type() == QEvent::Shortcut. Everything that couldn't be handled is then forwarded to QApplication::notify.

We didn't override the Ctrl+C shortcut or anything similar. However, because this is so early in Qt's signal handling you could be lucky with this approach.

@mrjj Thank you very much! Problem solved.

@Jarenward said in Fresh app development:

which Qt is for me?

There is only one Qt :-)
PyQt is a Python binding for Qt and still requires Qt libraries (binaries). So, even if you use PyQt you will need to have Qt libraries which you are using.
If I understood you correctly you need your UI on a computer (not Pi), right? This part is simple - just install the latest stable Qt version an start coding :-)
For the other part you can either directly develop on Pi (using Raspbian you can easily install Qt with apt) or you have to cross compile Qt to develop on your PC. You don't have to cross compile everything, just what you need. See https://wiki.qt.io/Raspberry_Pi_Beginners_Guide

Hi,

You are replacing the central widget in OpenVTK. You should rather add your widget to the current central widget's layout.

@Xenoshell
There is literally like one occurrence on the whole of the Interweb of your error in vainfo (va_openDriver() returns -1)!
https://bugs.launchpad.net/ubuntu/+source/libva-utils/+bug/1719150
It was suggested:

Please install mesa-va-drivers and try gain.

I suggest you try that.... :)

@Oatmeal I guess you already solved your issue since 9 months passed but I experienced same issue today and solved it eventually so I want to share it anyway. Instead of using below code
self.setFlag(QGraphicsItem.ItemIsMovable, True)
self.setFlag(QGraphicsItem.ItemIsSelectable, True)
self.setFlag(QGraphicsItem.ItemIsFocusable, True)
self.setFlag(QGraphicsItem.ItemSendsGeometryChanges, True)
using below code did the trick for me
setFlags(QGraphicsItem::ItemIsMovable | QGraphicsItem::ItemIsMovable | QGraphicsItem.ItemIsFocusable | QGraphicsItem::ItemSendsGeometryChanges);

Yeah i feel like i do sudo apt-get update && upgrade at least once a day. I just checked about SIP and i compiled it from source but i cant remember if i actually used the command make and make install. Does that mean i have to reinstall pyqt5 again? I guess i just open a new thread. Thanks for all the help @SGaist