General and Desktop

@SGaist Thank you. I didn't consider this. My mistake! Working much better now.

@AnneRanch said in Passing multiple parameters to QProcess: params need to have only single item... Not quite correct. params is a QStringList. A LIST of QString. With the << operator you direct the right side to the left (i.e. the string list). params need to have only single item... So it's more like "You can add only one after another" (because QProcess needs every argument as separate string) As you might already know / have seen from @Axel-Spoerl 's suggestion to use qDebug() This params << "-fa"; params << "Monospace"; params << "-fs"; params <<"16"; produces: QStringList("-fa") QStringList("-fa", "Monospace") QStringList("-fa", "Monospace", "-fs") QStringList("-fa", "Monospace", "-fs", "16") Each element is a QString and the next to-be-added item is appended to the end of the list.

@mrdebug said in Screensaver: XOpenDisplay I assume this only works for X11 and not Wayland?

@ChrisW67 said in McAfee identifies QtCore.pyd as virus and deleting: and matching cryptographic checksum Which as I said will change for a different version and likely be back where they were. Hopefully they will also identify what triggered the false positive and adapt their heuristics. Um.

Thank you for you help. @jsulm

@rtavakko if i have MINGW compiler..what i have to do

@ericarjun-t said in Moving Multiple Graphics Items with Keyboard Input.: I'm wondering if there is a clever way to just update the position of multiple QGraphicsItems (in my case, PixmapItems) with a single button press. Why not make every tetris item a block/class consisting out of multiple parts? As it is right now, you have just the parts forming the shape of your tetris item, but they are not connected and therefore only one part is moving. Make a new class for your tetris items and put your block logic inside paintEvent. To rotate the whole thing, you could use this instead of fiddling around with your own matrix. If you dont want to change your structure, you could maybe use QGraphicsItemGroup. https://doc.qt.io/qt-6/qgraphicsitemgroup.html#details

@JacobNovitsky It is auto-detected by Qt Creator and will come back even if you managed to delete it in (Edit > Preferences > Kits). Removing it in preferences will not remove it from existing projects. Just ignore it. Don't use it if you do not want to.

@SGaist Thank you for your response. My problem has been solved.

@JonB Id rather explore the QWebEngine mostly because, overall all the solutions found imply that we add the class definition each time we do sethtml . But I could do this easily without any custom class right. just using a long sequence of basic <></> before each message. So in essence, the custom class does not really work that well. Not to mention inserthtml does not take the custom class either, and we dont have access to all html functions either.

@Christian-Ehrlicher Thanks for your reply. I have tried removing them, and it still didn't work. However, I have solved the problem: I have to use Qt 6.5.3, and now I can see everything.

@DeadSo0ul Your code for adding "pages" to a QSW look correct. But you don't seem to have actually added the QSW itself anywhere onto the UI to be visible, just like you would need to for any QWidget! QSW itself is a QWidget, it just happens to show one of its child widgets at any one time So I would expect nothing to show in your code. The QSW does not belong in your LogIn class. It belongs on whatever widget you want to show the (choice of) widget instances, exactly where you would place the widgets and use show/hide() if you were doing that yourself. Let's say that is the central widget on a QMainWindow. Then over in your derived main window class you would have something like: #include <QWidget> #include "logIn.h" #include "someotherofyouruiclass.h" class MyMainWindow : QMainWindow; MyMainWindow::MyMainWindow(QWidget *parent /* = nullptr */) : QMainWindow(parent) { QStackedWidget *sw = new QStackedWidget(this); this->setCentralWidget(sw); sw->addWidget(new QTextEdit); // arbitrary, just to show what's possible sw->addWidget(new Login); // instance of your UI designed class sw->addWidget(new SomeOtherOfYourUiClass); // instance of a different UI designed class // you can do the following line here or e.g. in a main window button click slot sw->setCurrentIndex(1); // show your `Login` instead of the default one at index 0 }; If you are not attempting to show one of a choice of a widgets in the same place as each other then QSW is not your buddy. But I thought that is what you are wanting to do.

Hi and welcome :) @okhajut said in Variable that is updated whenever a button is presssed in Qt GUI application: could be declared inside the program's main You could, but makes no sense in this case. declared inside the MainWindow class private area That's what you should do. Depends on what you want to do further and where/for what the variable is used later. You might want to write some getters or add signals to it. Btw: If you only have some plain C knowledge, you should read about OOP and C++ basics first, before/while you start with Qt. https://www.w3schools.com/cpp/cpp_oop.asp https://www.w3schools.com/cpp/cpp_encapsulation.asp

@SGaist Thanks for your suggestion. I will try to implement things with QtQuick.

@SGaist Roger that

@StudentScripter these are standard cursors that users expect to see when they are doing drag and drop operation with item views.

@DrSnowLabs Sounds like there might be something to improve :-)

Hi, AFAIK, the selection model's currentChanged signal is connected for the combo box to work so it might just be that your edit triggers are shorted by this. Note that editing the content of a QComboBox dropdown would be pretty counter intuitive. What is your goal with that paradigm ?