@JonB thanks

Nevermind ! It worked !!!!!!! Thank you !!!

@jsulm @Christian-Ehrlicher signal/slot method working connect(this,&MainWindow::starting,onethread,&myThread::recvNum); onethread->start(); for(int i=1;i<5;i++) { emit starting(i); }

@Vivek_A This question seems to have nothing at all to do with Qt, does it? So shouldn't you ask at a mongodb forum?

my compiler is mingw32bit and mongocxx driver build in 64 bit . so thats make problem , i solved it by installing 64bit Qt.

You need to be more specific. xml doesn't have arrays, how should arrays be treated?

@Yash001 if your issue is solved (aside for the fact that you need to read and incorporate several concepts, I guess), please don't forget to mark this post as solved. Thanks.

got solution. before using the minimum size function set the windowstate Qt::WindowFullScreen. In my case I used line this->setWindowState(Qt::WindowFullScreen); before this->setMinimumWidth(1366); this->setMinimumHeight(768);.

@jsulm Tested on Ubuntu 18.04. I downloaded QML Poster Example and Annoted Url Example. After method isAvaible() all return false Debug: qt.nfc.neard: dbus object manager invalid qt.nfc.neard: Error getting managed objects qt.nfc.neard: dbus object manager invalid or adapter path invalid NFC not available

thanks !! . I will look into both of them

@aha_1980 Thanks!!

No need for another thread, I got it working. Here are the android related package versions which finally made it to work in case someone else has troubles: [image: 91e09f5d-3a2a-409d-ae8b-a84076d7a362.png] The latest JDK and NDK didn't work. I hope they fix the name strings for the next beta. It's annoying and confusing to have "GCC" everywhere even though it really uses clang.

Hi @jsulm and @Paul-Colby, if (segs) { delete[] segs; segs = nullptr; } This is an anti-pattern! Just make sure segs is nullptr before you call new and set it to nullptr after delete. No need to check for nullptr before delete: delete segs; segs = nullptr; Quoting the C++ Reference: "If this is a null-pointer, the function does nothing." Regards

@Geeva The easies way is to move your task into its own function that expects q QList<QString> as an argument: void myClass::myFunction(QList<QString> startvalue){ //do stuff eg: qDebug() << "Value Received from server :" << startvalue; QStringList first = startvalue.split("|"); int firstSize = first.size(); qDebug() << "size :" << firstSize; if(firstSize == 5){ first1 = first[2]; first2 = first[3]; }..........(continue) } then you call that function for each and every item in your QList<QList<QString>> QList<QList<QString> > myList for(QList<QString> ls : myList){ myFunction(ls); }

@Mahesh-Kumar-Kodanda said in QT 5.9 for i.MX6Q and Integrity RTOS build error - unrecognised command line option »-std=c++11«: cross compile tool chain For which device? You already use one- why do you ask me to provide one? A cross compile tool chain is not specific to Qt or any other framework/library but to a device.

'description' is not captured said that in your lambda, 'description' has not been captured... then add it on the list of captured elements: [this, captured] I red inside the answers that you may declare same name for function and variable... don't do that, it will generate problems for sure. QString 'description' declared here it is a clue for said that the answer of call this.getDescription() should be a QString (QString getDescription() const;) so 'description' has to be a QString (i think in private area of this). because you are not pass it, it is an undeclared new object inside your lambda function. so give a varaible name unik and pass the variable inside your lambda by the array list [....] should fix your problem.

@Blacktempel said: Is that an existing bug in "include" ? Is there currently no way to include external source files where the path has space[s] in it ? I'm not sure; I have never used the include() function with space-containing paths. You can ask the Qt engineers by subscribing to the Interest mailing list and posting there.

Hi, gcc's not alone. My old OS X clang isn't happy either with it.

If someone needs a comprehensive 8 pages long explanation for what's exactly happening here, I recommend reading "Item 22: When using the Pimpl Idiom, define special member functions in the implementation file" from "Effective Modern C++" by Scott Meyers.