@paulmasri said in Qt 6.2 + CMake + extending QML with a C++ class: I am building a standalone app (executable), so I think that what I'm after is a statically linked plugin. I don't believe so. If you're building a 'bundle-all' executable, you wouldn't need a plugin to begin with. I'd try something like this: qt_add_qml_module(People URI People VERSION 1.0 STATIC SOURCES Person.h Person.cpp NO_PLUGIN OUTPUT_TARGETS PEOPLE_DEPS ) target_link_library(myproject PRIVATE People ${PEOPLE_DEPS}) Also you may need to initialize the resources manually, as static builds are pita to begin with. Personally, I wouldn't do it. PS. Also remove the duplicating source files: qt_add_executable(myproject main.cpp Person.h Person.cpp #< Remove this )

See for example QTextCurso::setCharFormat.

Hi @JonB yes the selects are used as you've described. While waiting for answers I refound QxORM via Inqlude which looks like it has a soft deleted option so may more than do what I require. Thanks for the response

The issue was that it had to be byte \x05 and QByteArray.setnum(5) will result in \x35 so I had to use QByteArray::append()

@GrecKo said in Is it safe to bind to C++ subobject's property in QML?: But why don't you do property var qmlCompProp: database.getDbpointObject() in yout qmlComp? prop1 and prop2 are passed to the database.getDbpointObject(prop1, prop2) function. prop1 and prop2 are properties of qmlComp. These properties are set when an instance of qmlComp is created. Item { required property string prop1 property bool prop2: false property var qmlCompProp: ({}) Component.onCompleted: { qmlCompProp = database.getDbpointObject(prop1, prop2) } } Since the properties evaluation order is undefined, and qmlCompProp depends on both prop1 and prop2 values, I've opted to initialize qmlCompProp with an empty object and assign the actual object in Component.onCompleted. Is this the right/recommended way, or is there a better way to handle this? Thanks for the information about the warning and it's workaround.

I'll check back tomorrow or Tuesday to see if I can better explain the code that I am about to share. I'm in a hurry today, so I'm just going to paste this and hope that anyone reading it can make use of it :) #include <QQmlComponent> #include <QQmlProperty> #include <QQuickItem> void dumpRecursive( int level, QObject* object ) { if( object ) { QByteArray buf; buf.fill( ' ', level / 2 * 8 ); if( level % 2 ) buf += " "; QString name = object->objectName(); QVariant propv = QQmlProperty::read( object, "visible" ); if( propv.isNull() ) { fprintf( stderr, "%s\n", "IS_NULL visible prop" ); } else { QQmlProperty prop( object, "visible" ); fprintf( stderr, "hasNotifySignal %d\n", static_cast<int>( prop.hasNotifySignal() ) ); fprintf( stderr, "isResettable %d\n", static_cast<int>( prop.isResettable() ) ); fprintf( stderr, "isSignalProperty %d\n", static_cast<int>( prop.isSignalProperty() ) ); fprintf( stderr, "isValid %d\n", static_cast<int>( prop.isValid() ) ); fprintf( stderr, "isWritable %d\n", static_cast<int>( prop.isWritable() ) ); fprintf( stderr, "propertyTypeName %s\n", prop.propertyTypeName() ); fprintf( stderr, "needsNotifySignal %d\n", static_cast<int>( prop.needsNotifySignal() ) ); // bool QQmlProperty::needsNotifySignal() const // QMetaMethod m = prop.method(); } QVariant prop = QQmlProperty::read( object, "testtest" ); if( !prop.isNull() ) { if( !prop.canConvert<QList<QVariant>>() ) { fprintf( stderr, "%s\n", "whoooooooooooooooooooooooooops ! ! !" ); } else { QList<QVariant> list = prop.toList(); fprintf( stderr, "wheeeeeeeeeeeeeeeee %p\n", reinterpret_cast<void*>( &list ) ); for( const auto& state : list ) { fprintf( stderr, "got one %p\n", reinterpret_cast<void*>( &list ) ); if( state.canConvert<QQuickItem*>() ) { QQuickItem* t = state.value<QQuickItem*>(); fprintf( stderr, "converts one %p\n", reinterpret_cast<void*>( t ) ); } } } } qDebug( "%s%s::%s", reinterpret_cast<const char*>( buf.data() ), object->metaObject()->className(), name.toLocal8Bit().data() ); QObjectList children = object->children(); if( !children.isEmpty() ) { for( int i = 0; i < children.size(); ++i ) dumpRecursive( level + 1, children.at( i ) ); } } } void localDump( QObject* object ) { dumpRecursive( 0, object ); } // return true if the event should be filtered (i.e. stopped) bool EventFilter::eventFilter( QObject* obj, QEvent* event ) { localDump( obj ); return QObject::eventFilter( obj, event ); }

to continue the point @Christian-Ehrlicher mentioned above, blocking serial tasks usually exist on server daemon applications, but not on anything with user interaction or a GUI.

Bonjour, es-tu sûr que le jpg a la bonne taille et qu'il peut être affiché dans le QPushButton ? Voici une petite méthode pour mettre une icône à la bonne taille. Salutations de Vienne, où il fait froid, dans le lockdown. Axel QImage tint(QString icon, QColor color, qreal strength, int w, int h) { QImage src = QIcon(icon).pixmap(QSize(w,h)).toImage(); if(src.isNull()) return QImage(); QGraphicsScene scene; QGraphicsPixmapItem item; item.setPixmap(QPixmap::fromImage(src)); QGraphicsColorizeEffect effect; effect.setColor(color); effect.setStrength(strength); item.setGraphicsEffect(&effect); scene.addItem(&item); QImage res = src; QPainter ptr(&res); scene.render(&ptr, QRectF(), src.rect() ); return res; }

@Sai-Raul ok. but Qlabels only likes pixmaps.

@duckrae said in How to write another Thread data in txt file?: How can I handle it? Simply emit the signal: QTimer *timer = new QTimer(this) timer->start(60000); emit myTimeoutSignal(text);

@JonB Hi, sorry for the late reply. extacly, i already have signal parameter, only want to write generic mathod - which has its own inbuilt signal-side parameters for connect() but accepts the slot-side as parameters.

Does SLC.exe exist in that folder? You probably had a build failure; try to build your project again and see if there are any errors from that.

@mrjj I have the following stylesheet applied to a containing widget QMenu, QMenu QPushButton { background-color: #303030; color: white } When I remove the QMenu selector, the white line disappears (hence it starts looking like this) I cannot say whether the white line really disappears or it just blends with the white color of the menu item. After applying the same style with a QMenu::item selector, I get the following: The ordinary menu items are colored, but those created by my class are not. It appears as if the ::menuItem selector does not work on them. I also tried setting the following style rule on the container returned by the createWidget function container->setStyleSheet(".MenuItem {background-color: #303030; color: white; }"); and it oddly makes the custom menu items get shifted to the left and the hover effects on them do not seem to work any longer. Applying padding/margin does not fix it:

still in mingw way problem not solved . so i choose msvc compiler to do that .. so iam closing this ...

I have found partial "solution": QML can not correctly work with quint8 when it was typedefed and qRegistered. Changing initial type to quint32 solved the issue when QML can not correctly display its value. Passing Q_GADGET to QML via model's method data with using QVariant as a "transport" type works incorrectly (Q_GADGET inner variables cannot be changed for some reason), but passing it directly with separate model's method as Example getExpample(int index); works well. Anyway copying the Example's object in the both cases works well, but the last one allows to modify Example's members in QML. I can not say that my issue was solved (now I'm going to use quint32 and the second approach to pass Q_GADGET copy to QML), but I'm wondering, if this is a correct QML/QVariant/Q_GADGET behaviour to avoid such issues further.

You cannot, without modifying the class where the private member is declared. That's why it was made private. Without a get/set method pair it is only visible internally to the class.

First off, thanks for your time. I've tried that yeah - you can see that I've made the default index_file "qrc:/index-light.html" in the load_args function. It's here in the code. When writing to qDebug() the string is correctly "qrc:/index-light.html", though nothing is shown in the webview... I've tried changing it to "qrc:/light.css" and then it correctly shows the css in the webview (the code in plaintext).

@texasRanger said in read value from combo box to c++ function: I have been trying to connect the qml signal of the combo box being changed to the itemChanged slot in c++. but I have had no luck. Don't do that. Do like in the link posted by SGaist. Some links about the reason why you shouldn't reach into QML from C++: https://doc.qt.io/qt-5/qtquick-bestpractices.html#interacting-with-qml-from-c http://doc.qt.io/qt-5/qtqml-cppintegration-overview.html#interacting-with-qml-objects-from-c https://youtu.be/vzs5VPTf4QQ?t=23m20s

@ralphtink said in How to flatten a TreeView to show only the leaf node items?: I don't want to import a whole library just for this I would strongly suggest you do but even if you want to go against my advice you can just: take kbihash_p.h, kdescendantsproxymodel.h and kdescendantsproxymodel.cpp add the files to your project replace #include "kitemmodels_export.h" with #define KITEMMODELS_EXPORT satisfy LGPL 2 requirement on the imported code

@Ayush-Gupta said in How to write code using layout for this GUI ?: I tried this but it does not works. Spacing is still there. May be due to Install button alignment? Or, instead of what @VRonin suggested (which works BTW), you can make the grid layout with 4 columns. The install button would stretch over 2 columns and the line edit would stretch over 3 columns.

@JonB oh okay,i will try to make connect for it

@SGaist ok lemme try,if i understand what documentation say lol

@SGaist Thank you for your reponse. I will check both QtTestModule and Squish.

The stylesheet have their own internal style that does not care at all about the platform style be it the native one or fusion.

@KroMignon said in Cannot create new AVD for unknown reason: Okay... Thanks

I fixed this by setting QFont font = this->font(); to ui->appName->font(); in case anyone comes across this.

Hi Well you override the mouse functions and make it happen. virtual void mousePressEvent( QMouseEvent *e ); virtual void mouseMoveEvent( QMouseEvent *e ); virtual void mouseReleaseEvent( QMouseEvent *e ); have a look here https://gist.github.com/mnafees/10003130

@HenkKalkwater said in QML: QMetaProperty::read unable to handle for some enums defined in C++, but not all: Anyways, a huge thank you for your help. I´ve been stuck on this for about 2 days. Your welcome, I am glad I could help you :)

It has been clearly announced that the 6.0 release would not contain all modules.

@ELEMENTICY Click on "Edit" and take a look at main.cpp. I should have expressed that clearer: How does your code use/start that UI?

Hi, @WLOrion said in Introduction in Qwt: I didn't know this behavior of the Qwt Classes. This is nothing Qwt specific, it's part of the C++ basics. As for tutorial, there's a nice online book that is in German but the author claims that online translator should give you a good enough result in your own language.

@RekTekk249 said in Tons of error for no obvious reason: Two hours ago, everything was going well, until I realised I needed the same instance of my helper class in my MainWindow than in my LoginWindow. If you would have posted the whole file, esp. showing the parts you've changed, it would have saved a lot of troubleshooting ;-) It's also a debugging thing... If you made changes and suddenly nothing works anymore, revert the changes and try to figure out why it happened.

@fcarney Thanks. It solves my issue !

Hi @SGaist, I took you advice and finally found out where the problem is. I looked into Wependency Walker and realized that I can import PySide6.QWidgets before I import wiggly, So that the dlls needed is already loaded for wiggly. I've been testing wiggly using one single import wiggly in IPython, not runing the main.py directly in the examples, trying to copy dlls from one place to another, and kept getting ImportErrors. Now I write: import PySide6.QtWidget import wiggly and it works. Thanks for your help!