General and Desktop

@Peter_Dev Glad it worked for you. it's a solution I use very often. if everything is ok, pass this subject to resolved.

@nejatafshar said in What is the difference between qrc:/ and qrc:///: So which one is recommended the valid one. @nejatafshar said in What is the difference between qrc:/ and qrc:///: Is there any circumstances that the first one fails? yes as @Christian-Ehrlicher said, most likely it will fail if QUrl::ParsingMode is set to QUrl::StrictMode

@viniltc Hi No, overwrite means to add that function to your class so its called instead of the base class. void MainWindow:showEvent(QShowEvent *event) { QMainWindow::showEvent(event); // call base so we dont fux things up on_verticalSlider_valueChanged(100); }

Hi, Are you missing QT += charts in your .pro file ?

@Yunus Ok fine thanks

@jsulm sure

@KroMignon said in How to detect (inside) if my Qt app is running on a virtual machine: @Lemat If you virtual machine is a Windows system, you can read the manufacturer and model and look if it contains VMware or VirtualBox: wmic computersystem get manufacturer,name

Hi, Still the caching issue, it's marked properly. I see it as such.

Okay, I found a workaround: I define a CSS border for my QGroupBoxes which imitates thre Breeze look so that the native style isn't used, along with a property for the ones without a title, and I only use it if the Fusion style is used. main.cpp: if (application.style()->objectName() == QLatin1String("fusion")) { application.setStyleSheet(QStringLiteral(R"END( QGroupBox { border: 1px solid palette(Mid); border-radius: 2px; padding-top: 1.2em; } QGroupBox[notitle=true] { padding-top: 0; } QGroupBox::title { background-color: transparent; subcontrol-origin: margin; subcontrol-position: top center; padding: 0.4em 0 0; } QScrollArea { background-color: transparent; } )END")); } If a QGroupBox doesn't have a title, I define the notitle property: someBox->setProperty("notitle", true); The result is quite nice, although this is surely more a hack; but the only code to change are the setProperty calls that are simply ignored by the styles drawing the QGroupBoxes correctly: [image: b03b050e-592d-4a45-9215-3fd2133f974a.png] Well, it works ;-)

@J-Hilk A colleague of mine tried the 5.12.4, but the error is still there. I'll try with the QQuickPaintedItem or I'll switch to the 5.14. Thanks for your time.

@webzoid said in qRegisterMetaObject, SEGFAULT and QByteArray: The QSocketNotifier warning is from a QUdpSocket also contained within the application which is being created on one thread then polled on another thread. You must create the QTcp/UdpSocket in the thread you're reading/writing from. Everything else may work until it doesn't. Sharing a QTcpSocket (even guarded by a mutex) is not supported!

@JonB thanks

@SGaist , ok

@Yunus yeah sure i will check it..

Hi @N1coc4colA, You might want to have a look at this example. Regards

Looking at the docs, I don't see stackingMode property in QStackedWidget. So, use a layout instead. Put the stacked layout in your UI first, then add your big layout, and then the row layout with your small items. You'll need to throw a spacer or dummy layout item into that row layout to keep the big space on the left clean.

@Robert-Hairgrove the caching issue is currently really a big problem - since I was aware of it I even hit 'F5' before I wrote the post but it did not help :)

@SimonF said in QChart, do I need to delete chart series by myself? [Memory leak]: Doesn't Qt basically come with it's "own" memory management system? Qt has parent/child relation ship (https://doc.qt.io/qt-5/objecttrees.html) and parent deletes its children when it is destroyed. But that's all. For everything else usual C++ rules apply. Shared pointers should not be used for example for everything managed by parent/child relationship (for example widgets).