@JonB said in Connection signals for dynamically created widgets: Bit it does not! QGraphicsItems do not inherit QObject, only QGraphicsObjects do. You're right! I got confused when going up the inheritance tree in the documentation, I clicked on "inherited by QGraphicsObject" at some point thinking it was "inherits" instead. I didn't specify in a written manner that my StateWidget was a QGraphicsEllipseItem as I had added the declaration of the class in the first message. I changed the class to inherit QObject as well though and it worked! class StateWidget : public QObject, public QGraphicsEllipseItem { ... } The order of inheritance is important too. The "Test n" below comes from the AutomatLab::StateParams function so the signal is properly forwarded to the main UI instance! [image: 973931d7-e484-4597-8d82-5c6be4cefda8.png] Thank you for your help!

Based on the pkexec documentation you can't do what you are trying. The environment is set to a minimal state that excludes the variables you are interested in. If you want their values in your application, you will have to pass them as command line parameters. However, based on the variable you are looking for, it seems you want to run a GUI as root, which is usually a bad idea.

I have since found out that grabWindow doesn’t work under Wayland. So I either have to find another way or resort to X11 again.

@Aditya-Gupta said in Struggling Trying to Transfer Project from old laptop to new laptop: the red icon persisted And what does it say if you put mouse cursor over it?

@Christian-Ehrlicher said in Dynamic XML documents instead of `.ui` files in Qt: @brainchild The uiloader is just a way to load xml files which in 99,9% are processed by uic and compiled directly instead. So adding this complexity to pass a DOM instead a simple QIODevice for the max. 0,1% use case is fine in my pov. Esp.since there is no need for a DOM and QtCore don't have a DOM class at all - QXmlStreamReader is perfectly fine for this simple task. The XML module has a DOM representation. Why would it not be sensible for a version to be provided of load() that processes a DOM representation from this module?

Qt integrates very well with OpenGL so I am unsure what you think you would be missing ? That said, another possible way to do what you want could be the Graphics View Framework.

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

It's been solved by create a process and launch the QOpenGLWidget's .exe file.

@Aahi You don't have to use this old connection style. Remove SIGNAL and SLOT words. auto window2 = new MainWindow(); connect(ui->pushButton, &QPushButton::pressed, window2, &MainWindow::some_slot_that_you_have_in_MainWindow_class); some_slot_that_you_have_in_MainWindow_class() { ui->checkBox->setChecked(false); } Something like that

@JPolo said in Unable to compile when using QCustomPlot: I use Qt Creator 4.15.0 based on Qt 5.15.2 MSVC2019 That is not necesserilly Qt version you're using (this is the Qt version used to build QtCreator). What Qt version did you install? What is the first error message? Did you do what the tutorial suggests: "To use the shared library in your application, set the define QCUSTOMPLOT_USE_LIBRARY before including the QCustomPlot header."?

Right ! Your part was way longer than the original conversation 😅

Hi, On macOS you have that option integrated through Sidecar. On Windows, there are several possibilities existing. Do you really want to re-implement that ?

@umen242 you probably need parts of several QGraphicsView examples

Did you consider using the QtGraphicalEffects module ?

Hi, You might want to check KDAB's KDSoap library.

Thank you, I got it.

@Yalimyulad said in Post installing Qmake for new devices: Is it possible to somehow copy the Qmake I have built from raspberry pi to my desktop? Nothing is physically stopping you, but it won't work. qmake is created and specific to the Qt FrameWork/Compiler used for that framework. The compiler on your pi is not the same as the one you would use for cross compiling If you want to really cross compile for the Pi , you will have to jump through some loops. There are some guides out there for example this wiki entries https://wiki.qt.io/Raspberry_Pi_Beginners_Guide https://wiki.qt.io/RaspberryPi2EGLFS

@J-Hilk @aha_1980 I think i failed to see simplicity of this one. thank you for guidence.

Hi, You should take a look at the QtSystems module.