General and Desktop

I stumbled upon this topic while looking for a similar solution. Since it didn't exist, we created it: https://github.com/planed-es/QXmlSec It uses xmlsec-openssl to verify or generate XML digital signature using QSslKey (and we also have our own types, as QSslKey doesn't support all the formats supported by xmlsec) and QDomDocument. I sure hope this will be helpful for other developers !

Faced the same need. Qt 5.15 or newer. Since Qt is declared cross-platform it would be nice to have platform-independent way...

FWIW, I found my problem (and it was my bad). There may have been a change in how things were done, and some legacy build scripts were confused by it, but it looks like it came down to the install. The tricky part is that when you use --development-build on configure, it performs an "install" automatically into the source folders under qtbase. That's what I was used to seeing - this pseudo install where everything is lined up under qtbase. When you create a release build, you typically use a --prefix to specify the destination for your install. So I was looking in qtbase for my complete install, when It was in fact in a completely separate folder as recommended on the docs. It was just a matter of getting my nose back in the documentation. To me, it looked like some kind of bug or incomplete setup, when in fact, I was just looking in the wrong place. Thanks for the feedback, but this was user error.

Thankyou JonB- this is working fine now. Terrific! Here's how it looks now in the example code: self.stacked_widget = QStackedWidget() self.setCentralWidget(self.stacked_widget) self.stacked_widget.addWidget(self.graphics_scene_1) self.stacked_widget.addWidget(self.graphics_scene_2) Now I can swap between scenes without issues with: self.stacked_widget.setCurrentIndex(1) self.stacked_widget.setCurrentIndex(0) etc... Cheers!

There is no such capability in QColorDialog. You may need to implement a dialog yourself or rethink how this "uncolouring" mechanism should work.

I think you can't do that. Take a look at https://www.qt.io/blog/2012/09/28/qt-support-weekly-27-widgets-on-a-header about writing a custom headerView with widgets.

Nice ! I agree with your suggestion. Did you already check the bug report system about that matter ? If there's nothing there, you could open a feature request to improve that message.

Thank you for your reply. Will have a peek at it.

@Ramkumar-Mohan said in How to use Arithmetic Operators with HexaDecimal Value in c++?: It comes if you type the 4D value manually and use it. I have put that 4D hex value in string list how to use 4D data (0x4D) in string list here. i have no idea . And I've not a single idea what you want to do and where your problem is. Please properly describe what you want to do (and with what) and where your problem is.

@JonB said in Recursion on object creation: @Nick-Shapper No, there is not (that I am aware of). This is not specifically a Qt issue, it is general design principles that I and others have learned over a lifetime of programming! :) You might look up general "OOP" (object-oriented programming) principles. Your principle of encapsulating access between classes via getter & setter methods was already good. It's just that it's not something to use to gain access to the main window! That may be a "parent" to other QObjects (e.g. passed as parent to Player's constructor), but the general rule is that parents may access child methods but children should not, and should not need to, access their parent. Try to design Player so that it might be used from anywhere, e.g. it should still function if, say, there were no main window to call. In any case, the most important lesson to learn here is that passing a pointer to an existing object/instance is quite different from creating a brand new object/instance. Even if your code had not crashed, the result returned by window::volume() on your freshly created MainWindow instance would have borne no relationship to the value of the slider in the actual MainWindow instance already in existence. Ok, now that makes sense. So basically i gotta design Player so that it would be completely independent and also could be used from anywhere, right?

You should tell us more - e.g. what you're trying to do would be a good start. /utf-8 is a msvc switch but you obviously try to compile with gcc - this will not work.

@Francky033 said in Observations about Qt 6.4 ...: How to do in this kind of situation? Create a minimal, compilable example e.g. by reducing your code until the erorr no longer occours. Daily's programmers business.

Thank you @ChrisW67 Qt Creator and Qt was installed from Qt sources, however, the person that installed ignored the warnings and dependencies, so some packages weren't installed. I am enabling Code Ready for RHEL and installing the required dependencies that are missing. I also think that RHEL isn't the right OS for development.

solved with case QAbstractOAuth::Stage::RequestingAccessToken: params->insert("code", params->value("code")); params->insert("redirect_uri", "http://localhost:5000/Callback"); params->insert("scope", "openid offline_access bcf"); params->insert("code_challenge_method", "S256"); break;

@jsulm [solved] Thanks. I have corrected it to, QGraphicsTextItem* textItem = new QGraphicsTextItem("New user"); textItem->setFlag(QGraphicsItem::ItemIsMovable); textItem->setFlag(QGraphicsItem::ItemIsSelectable); textItem->setTextInteractionFlags(Qt::TextEditorInteraction); connect(textItem->document(), &QTextDocument::contentsChanged, this, &MainWindow::textcontentsChanged); It's working now.

Turns out I was not registering the Dummy class on client side due to which client was not able to recognize the type. qRegisterMetaType needs to be used at both ends.

This question is duplicate of your another qn. May be you can delete this question.

@Christian-Ehrlicher said in QSqlQuery & parameters: If you want the source code for it - qsqlresult.cpp OK - thank you. This is it. line 161 and around that - is quite clear. I still not completly agree on the docu - but the code shows, that Qt does not use the named placeholders of the drivers at all - but only simulates it, kind of. Not sure, if I think this is good, but - it is what it is. So - who said it: this is Qt and not Sqlite. Thx for all contributions! I will mark this solved