General and Desktop

Why don't you use QGraphicsSvgItem instead? Using a proxy widget will add all kinds of nasty surprises, one of them being that the content of the embedded widget does not scale nicely by default.

Hi What code do you have now? Anyway, something like this https://amin-ahmadi.com/2016/01/04/qt-drag-drop-files-images/

What did you implement to make it work ?

Dupe of https://forum.qt.io/topic/125644/qt-6-0-adaptation-warning-string-is-deprecated-use-qmetatype-type-instead-how-to-solve ... wonder why it's so hard to read the error message. It contains the answer...

Hi, The answer is in the warning: QMetaType::Type enumeration.

QProcess has quite extensive support for synchronous use. #include <QCoreApplication> #include <QDebug> #include <QProcess> int main(int argc, char **argv) { QCoreApplication app(argc, argv); QProcess process; process.start("ls", {"-l"}); if (process.waitForFinished()) { qDebug() << "returned:" << process.readAllStandardOutput(); } else { qDebug() << process.errorString(); } process.start("ls", {"-l"}); while (process.waitForReadyRead()) { while (process.canReadLine()) qDebug() << process.readLine().trimmed(); } }

Alright I had some stuff commented out that took me forever to debug, but I got it! So the piece I was missing is that a View has both a Model and a SelectionModel. Obviously this is listed in the documentation, but I missed it. Here's the chunk of documentation regarding that: Handling selections of items The mechanism for handling selections of items within views is provided by the QItemSelectionModel class. All of the standard views construct their own selection models by default, and interact with them in the normal way. The selection model being used by a view can be obtained through the selectionModel() function, and a replacement selection model can be specified with setSelectionModel(). The ability to control the selection model used by a view is useful when we want to provide multiple consistent views onto the same model data. Anyway, so it turns out all I needed was a subclass of QStringListModel to handle my data that I had already made, and I got lost in the sauce trying to turn that into a QItemSelectionModel, thinking it was a direct replacement for a Model. I guess I feel like it could be more clear that a View has both a Model and a SelectionModel attached as soon as you give it a Model, but it's there in the docs so I guess it's on me. :) Thanks for the help!

@Donald-Duck said in Cross-compiling Qt for Linux on Windows: it worked. great. So please don't forget to mark your post as solved!

@nagesh thank you it solved i did the QRegisterMetaType just before connecting the signal to slot

One mediocre fix would be to set the stylesheet of the vertical scoll bar to have enough padding at the top. However, this will not extend the header view all the way to the right. Another quick hack would be the following: permanently disable the vertical scrollbar of the table widget create your own QScrollBar which you place perfectly on top of the QTableWidget subscribe to the the table widget's resize and move events to resize and move your scrollbar accordingly (use inheritance or use installEventFilter() to be notified of size/position changes) connect your own scrollbar back to the table widget

I would really suggest to go with a stylesheet. I don't see a reason why not (never had any issues that it would be too slow or anything). Changing the palette might work for some widget types on some platforms. If you use the native style on Windows or Mac OS you will eventually run into problems that you cannot change any part of the palette to influence some of the colors. You could try to use proxy styles to change colors of certain widgets. But, this is very messy compared to just plain stylesheets. Qt used to have setBackgroundColor() at one point, but it slowly faded out. So, as long as you don't have any specific good reason to not use stylesheets, go with stylesheets as they will make your life a lot easier. (I personally wish as well that we did not have to use stylesheets. After fighting it for quite a while I finally gave in because there is no better way in Qt.)

@AuLoMa said in How to detect mainWindow size changment ?: I don't find any slot or signal for this. See QWidget::resizeEvent()

@m4t1 Did you try export LD_LIBRARY_PATH=HERE_PATH_TO_QT_LIBS_DIR && ./my_app ?

It is solved - I had to find some updates for external libraries and the problem was gone.

@SGaist mmh 🤔 right, May be a better approach, than what I currently have. I'll have to test it. Thanks!

Dupe of https://bugreports.qt.io/browse/QTBUG-13522 - don't use widgets in itemviews. We really should have deprecate this widget inside item views stuff in Qt6...

@canid as per qt doc.. On Windows, for 32-bit programs running in WOW64 mode, settings are stored in the following registry path: HKEY_LOCAL_MACHINE\Software\WOW6432node I feel 32 bit & 64 bit application registry locations are different..

@georgiav said in Running qt on external computer: Can I run my program on an external computer that doesn't have qt? Yes you can. Just deploy your application: https://doc.qt.io/qt-5/deployment.html for the open source version of qt, the application built can be run only within Qt , right? Nope, for 2 different reasons: The whole purpose of free and open-source software is to guarantee freedoms to users. So, you have the freedom to run the application anywhere you want. You're thinking about running the application within Qt Creator, the IDE (Integrated Development Environment). Qt is a library. Qt is not Qt Creator.