General and Desktop

Do you emit your signal anywhere? If not, then your slot will never be called.

@Youenn Great! Don't forget to mark this topic as solved.

@JonB I didn't replace, I just checked if it works. I think I'll just make a new file or download 6.6.0. Since it's my first try - nothing critical about it. Thanks a lot for your help!

@MyNameIsQt I don't know how it works for the online installer or Windows, but is QtWebEngine/Widgets an optional part for installing, i.e. are you sure you have it installed? Also, you only show that your Qt Creator was compiled with MSVC 2019. That says nothing about what Qt you are compiling against or what compiler you are using? If you use MinGW at all, or an MSVC older than 2017, it won't work and you will get this message.

@Ylvy I think you will find the whole point is that you must put the qputenv() statement before the line creating the QApplication so that the application respects your desired media backend!

@clarify QT_VERSION is defined. #if QT_VERSION >= 0x060000 #if QT_VERSION >= QT_VERSION_CHECK(6, 0, 0)

@giorgik63 said in How to change property value to my custom widget ?: It compiles just fine for me. Really? Let's look at QImageSvg::ledShape QLedNew::shape() const { return shape; } No type QImageSvg::ledShape has been defined. This defines a method in the QLedNew class. No such class has been declared. The method QImageSvg::shape(), declared in the header file for class QImageSvg, has not been defined anywhere. In its body there is no such variable as shape for the return statement. If this is really the code you have, with other stuff to make it compile, perhaps it has some relationship to your problem....

@ocgltd said in qmake not finding right mkspec: Why is the spec folder not found? Have you run install target after compiling Qt?

Hi, Do you mean draw on a different widget ? If so, you can't. What you can do is use a larger widget so you have a larger surface to use.

I searched this a bit more. First of all the behavior might be depending on OS. (Noticed some differences on Unix vs Windows) Secondly, I created a timer that every 2 seconds prints out qApp->focusObject(). It looks like after a QEvent::ApplicationStateChange and a QEvent::WindowDeactivate that all the widgets receive afterwards, the qApp->focusObject() is always nullptr. And after nullptr Qt selects the widget on MainWindow that was the last widget to have focus, and gives focus there. So I feel that subwindows are ignored somehow... I am leaving this open for a bit, in case someone has a good solution to track if a subwindow had focus, it should regain it after application re activation.

Using Google translate: 话题转移到相应的国际部分。其他子论坛请使用英语，因为它是论坛的官方语言。

@Abderrahmene_Rayene thank you so much, i am continue to try

@Abderrahmene_Rayene For just the data in editable widgets, this should be doable via some model and then that could potentially be synced I guess. That might be supported by your QtDataSync link, it mentions "Qt "model" class (QAbstractListModel) to view store data in item views".

@LT-K101 I have never used QtCharts but take a look at how it's done in https://doc.qt.io/qt-6/qtcharts-barchart-example.html. You have one QBarSet with multiple items in it. That causes your "separate groups". You want multiple QBarSets (one for each printer) each with just one item/value (printer[1]) in it. That will "group" them together.