General and Desktop

@Creaperdown said in How to pass QNetworkReply‘s data without copying it into memory: file that QNetworkReply There is no file. The incoming data is put into a buffer from which you then read it. Ideally you simply connect a slot to https://doc.qt.io/qt-6/qiodevice.html#readyRead of your QNetworkReply and read the data every time this slot is called.

Maybe related to https://bugreports.qt.io/browse/QTBUG-93631?

@sporefan perhaps make your pure C++ projects again but with Qt this time, you already have those ideas which should be quite advanced (considering your own estimation of your C++ skills), and even better, see if Qt offers a way to make them better, or add more features to them, don't start fresh, build from what you already made with pure C++.

@bigguiness Basically, get a QScreen, and then call setScreen on the widget you want moved to that screen: https://doc.qt.io/qt-6/qwidget.html#setScreen You probably want to do it before the widget is shown.

What was the issue ?

I am suggesting that you install the Qt development packages from your distribution and use that version of Qt to build your application. You don't have to build anything (beside your application).

Hi all and thanks a lot! After, again, installing from scratch Debian and the QtCreator it seems to run :-) No idea why but, at least, the pure widget program skeleton (Create Project) runs and shows the empty window :-) Thanks again!

Hi, @astoffregen said in QT USB support: @Christian-Ehrlicher An usb stick This likely means a storage device but a USB stick can be: Storage Bluetooth dongle WiFi dongle Serial port etc. Depending on your exact needs, KDE's Solid framework might be of interest.

@_bmb For anyone's reference, I've found a good solution is to not use QPainterPath at all, and simply store a QList of QLines (about 30,000 of them for my data), and draw them using QPainter. I put pointers to these lists in a vector, so I can keep track of multiple data sets on the graph if I want. In order to check for mouse hover events over my data, I create a tiny diagonal line at the current mouse position, iterate through the entire list of 30,000 lines and check each for intersections. Surprisingly, this is a very fast operation and I'm noticing zero lag, even with multiple data sets on the graph. The benefit of using QLines is that you can return the actual intersection location, which QPainterPath intersections are apparently not capable of.

@Perdrix said in Clipping of (OR maybe background colour of) QToolbar Icons: Why did adding border:none; fix it please? QSS magic/guess/example/makes sense to remove anything not needed.

@Bhavith-C You can use Visual Studio Code, Visual Studio or CLion if you find Qt Creator shitty. There are alternatives, but for some of them you may have to pay...

@mrjj Thanks. Your suggestion worked.

@mbatra Exactly as @jsulm has written. If the file to be monitored does not yet exist you cannot place a QFileSystemWatcher on it. You have to watch the directory first to see file creation via directoryChanged(). Only once it has been created can you then start to monitor the file for fileChanged(), so a two-step process for your case.

@JonB Minimal project as you requested github I have to say that this works :D But then I managed to make it not work again, ViewportUpdateMode set to NoViewportUpdate QGraphicsView will never update its viewport when the scene changes; the user is expected to control all updates. This mode disables all (potentially slow) item visibility testing in QGraphicsView, and is suitable for scenes that either require a fixed frame rate, or where the viewport is otherwise updated externally. That surprised me because descriptions says that the user is expected to control all updates, so I thought that calling a QGraphicsItem::update() will propagate this to a scene() but I guess not. Well this thread can be closed then, hope someone in the future will not waste 2 days trying to fix it

I've reported this as a bug: https://bugreports.qt.io/browse/QTBUG-112654 and closed it as Invalid! A minimum size was set slightly low ...