You have placed the radio buttons in the layout of the widget that contains the QLabel image. Widgets in a layout are positioned at run time by the layout logic and will not overlap. If you want to position a QRadiobutton visibly on top of another widget (i.e on top of the QLabel image of Puerto Rico beach) then:

The parent widget of the QRadioButtons should be the QLabel. This ensures the on-top-of element but cannot easily be achieved in Designer because it does not consider QLabel a container. The QRadioButtons cannot be in a layout. Positioning the buttons is absolute and you are responsible for adjusting it if the label is resized.

It can be achieved with a bit of code. Either:

Put the QRadioButtions into the Designer UI layout then, in the form widget code after calling setupUI(), change their parentage and position (which will be relative to the label content area). Leave the QRadioButtons out of the Designer UI then create and position the radio buttons after setupUI() Build the whole UI in code.

AS @JonB said,
Python is a dynamic language, C++ is not.
So, you need to make an explicit cast to retreive the type of object you want.
If you expect e->source() to return a QTabWidget, you need to do:

QTabWidget* tabWidget=qobject_cast<QTabWidget*>(e->source()); if(tabWidget) // is a tab widget ? ( // indeed it is ) else { // is not }

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

@Pythonic-person Unreal Engine allows you to build it as a library and embed into another app, provided that you can drive it. It needs native window messages and I'm not versed enough in python to give you specifics, but it sounds doable. Make sure to read through the UE EULA though, to be sure that whatever you plan to do is legally allowed by Epic.

Just as a comment though. You chose a very slow language (python) to do very expensive task (3D), bind it to a C++ library (pyqt), which adds overhead, interoperate it with external app that has no direct python API, and then drive it with native OS messages in a language that is not directly supported by that platform. In short you chose to do it the hardest and slowest possible way before you even started. It's your decision of course, but I would seriously reconsider.

@JonB In command line, we usually kill a mpi program by killing one of the child processes. And I find this may be a bug of intel mpi on windows [ https://community.intel.com/t5/Intel-oneAPI-HPC-Toolkit/InteloneAPI-MPI-2021-2-0-behavior-on-Linux-and-Windows-differ/td-p/1290020 ]. Anyway, thanks for your reply.

Hi,

Check the file content
Check the file permissions
Etc.

@JonB ok. I'm picking up what you're laying down. I went through my code and made sure my structure is actually following the patterns I've decided on. To answer your question, I do need access to both the proxy model and source model, but thanks for clarifying the distinction. Thank you for your time!

use splash widget?
https://doc.qt.io/qt-6/qsplashscreen.html

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.

The smoothing done for the antialiasing will not be the same for all colors.

The short version would be to add a set_i2c_data method to your model, update the data frame in it and then emit the dataChanged signal as last step of that method.

Hi,

That's because these classes are no widgets, there are used to build the UI.

In you code snippet, you would use self.nextui.hide() to hide the widget that was created with the help of Registration.Ui_Registration. That is the same for all the widgets you created that way.

thank you sir for your help

Interface is the keyword here: interface != widget.

You build a widget with the interface you defined but the interface itself is not a widget.

@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.

Yes, Qt.EditRole and Qt.DisplayRole are the same thing in non-customised Qt classes

Depending on your end goal, you might want to consider using a library like OpenCV to do the zooming part and Qt to display the result.