General and Desktop

@kshegunov One might actually need the signal to tell us which flags have changed. Only certain flag changes affect anything we are interested in, several seem not relevant.

@ThThoma said in Detect top/parent move event on child widget: However, what if I have multiple floating widgets that track their "parent" movements? You'd have multiple event filters. And I'm answering: probably the delay from the multiple filters will start to get noticeable... I really doubt it, as long as you don't have too many. If you keep the event processing responsive, you shouldn't notice it at all. Personally, I'd rather have the window in a layout, or if it's really floating, then leave it be, but ymmv.

@AlexMax The issues is marked fixed in 6.3 and 6.4, so it it still persists in 6.5, that would probably warrant a new issue, linking to the old one. Or is it captured by linked and still-open https://bugreports.qt.io/browse/QTBUG-99602?

@Bonnie Thank you, I can't believe I didn't think of that. Now it works like a charm, thanks again!

@Chris-Kawa , Thank you. that's the solution.

@cainiao123 You might install, say, the latest version of Creator instead of one from 2017. the project in Linux virtual machine， It would be an awful lot simpler to just do the editing/development in the Linux VM, given that is what you already have....

Finally, found a solution! The trick is Not to use hover modifier/attribute for disabled items QListWidget::item:disabled, QListWidget::item:!active, {background: transparent;} This stylesheet plus removing IsEnabled or IsSelectable flag for desired items will disable hover effect.

Yinz are probly already aware of this but I think it is important to note...from the QThread documentation: The effect of the priority parameter is dependent on the operating system's scheduling policy. In particular, the priority will be ignored on systems that do not support thread priorities (such as on Linux, see http://linux.die.net/man/2/sched_setscheduler for more details).

Not sure if it will help in your case, but @hskoglund has some solution to run Qt6 on Windows 7, see here: https://forum.qt.io/topic/133002/qt-creator-6-0-1-and-qt-6-2-2-running-on-windows-7 Regarding D3D requirement, I think for widgets it should be possible to not have it (widgets are drawn using software renderer anyway). See https://doc.qt.io/qt-6/qtquick-visualcanvas-scenegraph-renderer.html#rendering-via-the-qt-rendering-hardware-interface and https://doc.qt.io/qt-6/opengl-changes-qt6.html

Hi, Did you already check the Quick Subscription example ?

Add all the modules to the target_link_libraries call.

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!