General and Desktop

Thanks for the info, upgrading to Qt Plugin 2.6.0.7 seems to have fixed this issue for me.

@JonB Thanks for your time!

Hi, In addition to @sierdzio, KDiff3 might also be of interest.

@sierdzio thanks, I completely missed it. If you want to go with the latest and greatest of Plasma, then you should consider using KDE Neon. It's an Ubuntu based distribution which provides Plasma up to date. You have the choice between the standard, developer and unstable variants. It will likely cover your needs.

ok, thank you

Hi, The coordinate system is not based on the center of what you want to paint. Please take a look at the corresponding chapter in Qt's documentation.

Hi, Thank you for your reply. So, I will layout application again.

@ted19b I'm the person who's interested in this :) Thanks for all your replies/links. This means that the problem certainly comes from my code. Glad you have discovered this. When I looked at the https://code.woboq.org/qt5/qtbase/src/corelib/io/qdir.cpp.html#_ZN4QDir17removeRecursivelyEv implementation I could only see it doing non-creationtime operations, so your findings now correspond :)

@Bonnie Wouv that's it! You ve got the point. It seems that i clicked over an empty field next to my qlabel (which corresponds the form) and then set its stylesheet but i didn't notice that it is not my qlabel. With your correct answer, my question now seems to be a very foolish one :) but thanks a lot, you saved my day

@Martmists said in How to affect GUIs across threads: Are there any methods for "queueing" changes across threads for such applications Of course: signals/slots with Qt::QueuedConnection connection type, see https://doc.qt.io/qt-5/qt.html#ConnectionType-enum. Qt::QueuedConnection is default when connecting signals/slots between different threads. Important rule: never change UI from other threads than UI thread. So, simply emit signals from your audio thread and connect these signals to slots in your UI thread where you then change the UI.

@KH-219Design Okay great I will take a look over this and see if I can get it working as well, thank you!

The cumulation is correct but not the loop. Once you got the data, check for the frame. If not there, let your application live and the next time readyRead is fired, it will do the same and you might have there the complete frame. No need for a tight loop.

Perfect that worked, thank you!

Thanks! A call to setObjectName solved the problem.

@SGaist It's large binary data (100MB). While QLocalServer is quite fast, still its a bit of an overhead having to pipe all the data through a socket. I guess I'll load data in shared memory and then notify other side over QLocalSocket