@Emrecp I believe @SGaist is telling you that you cannot guarantee that a widget with a stylesheet will look identical to one you construct with coded style attributes. As soon as you place a stylesheet on a widget you are (potentially) losing some styles which are inbuilt, so it may differ. I suggested earlier you remove the weight stuff in your example and see whether just with the font in "normal" it does or does not look identical using the same font in both code and stylesheet. If you are coding inside paintEvent() then, as you say, you cannot use stylesheet. You can only set the attributes on a QFont as you have done. I don't know whether you can go through the sources of Qt to discover just what a current style like Fusion does.

@BigBen When you go QMenu::addAction("SomeString") it creates a QAction for you, and returns it. And QMenu::exec() returns the QAction which was clicked. So you could check which one is returned and act on it, like: QAction *hideAction = myMenu.addAction("Hide"); QAction *showAction = myMenu.addAction("Show"); QAction* selectedAction = myMenu.exec(globalPos); if (selectedAction == hideAction) qInfo() << "Hide"; else if (selectedAction == showAction) qInfo() << "Show"; Alternatively, when you create the QActions you could attach a slot to its triggered signal: connect(hideAction, &QAction::triggered, this, []() { qInfo() << "Hide"; } );

The tag support in Qt objects is really simplistic and nowhere near like a browser. If you want browser type html use webengine. I think webengine is pretty heavy and probably not what you want.

Anyone? T_T

I found out that I can reproduce this behavior by setting QT_DISTANCEFIELD_DEFAULT_BASEFONTSIZE, QT_DISTANCEFIELD_DEFAULT_SCALE and QT_DISTANCEFIELD_DEFAULT_RADIUS variables. With these, the problem occurs even on Windows. Not sure whether it's the same problem or not, but if QT_DISTANCEFIELD_DEFAULT_RADIUS is NOT DIVISIBLE by QT_DISTANCEFIELD_DEFAULT_SCALE, the problem occurs 100% of time (some letters will disappear). Example: export QT_DISTANCEFIELD_DEFAULT_BASEFONTSIZE=128 export QT_DISTANCEFIELD_DEFAULT_SCALE=12 export QT_DISTANCEFIELD_DEFAULT_RADIUS=96 // If I set this to 95 or 97 or anything not divisible by 12, it will break. Can someone explain me what these distancefield environment variables do and whether this is an intended behavior?

The question is very general. So what exactly is the problem you cannot solve, and what have you coded so far?

@maxime.armand Have you actually tried it? It does exactly what you demand in step 1. And if you look in http://doc.qt.io/qt-5/qtserialport-creaderasync-main-cpp.html you will see that the serial port and the baud rate are given as command line parameters. Just (cross-)compile the program for the Raspberry, and run it. It should work like your HypterTerminal test.

you can send the string to other class by simply placing it in the Signal, and catch the signal at the other class.

@mrjj as i told you in the thread, it looks the same as on your picture. But it should be transparent, so you can see the code lines from the editor below in your case. But let's continue that in the other thread

@SGaist I edited, thanks

I solved my problem by using this line: if(tmp=="PassDialog") { //QLabel* lbl = f->findChild<QLabel*>("lblRFID"); MyDialog *tempDialog = qobject_cast<MyDialog*>(f); tempDialog->AcceptCard(output); // emit recRFID(output); return; } and clean that connection and comment the emit code. now its worked. But I don't know why that code has error.

@tomasz3dk Wielkie dzięki, pomogło :)