@Sachin-Bhatt My explanation: True evaluates to 1 in a numerical context. False evaluates to 0. So:

True +3 = 4 1 + 4 = 5 2 + False = 2

@jsulm Thank you. That works. What could have been the problem? That C Arrays are not compatible for the container classes?

@SGaist okey i will try

Thanks guys!
Im on Qt 5.10, that explains why the "=>" is not working. Had not known about the old style syntax.

Settings this to closed.

@illud

Do you think after 6 years, he's still looking for a solution? ;-)
The topic is marked "solved" anyway :-)

@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); }

@Lasith
Hi
old type c array can also work.
Its just a matter of what is registered already.
You can register your own types.

http://doc.qt.io/qt-5/qmetatype.html#Q_DECLARE_METATYPE

@J.Hilk Thanx alot

@VRonin
i before write my code to this method 369 book:

void WeatherBalloon::sendDatagram() { QByteArray datagram; QDataStream out(&datagram, QIODevice::WriteOnly); out.setVersion(QDataStream::Qt_4_3); out << QDateTime::currentDateTime() << temperature() << humidity() << altitude(); udpSocket.writeDatagram(datagram, QHostAddress::LocalHost, 5824); }

But we want to connect UDP processing data to GUI app, it can not read QDataStream Method and it Crashs. The app is written in C#,So we should try a method that work with VisualStudio.
Agian Than kyou for attention
best regards stackprogramer

Hi @Alper,
Here is what works.
Use ScrollView instead of Flickable for scrollbars. Then as per this we need to explicitly set the contentItem as this newly created component.
A very minimal example:

import QtQuick 2.6 import QtQuick.Controls 1.4 Item { id: root width: 200 height: 200 ScrollView { id: scroll anchors.fill: parent } Button { text: "Load" onClicked: { var component = Qt.createComponent("Dummy.qml"); var obj = component.createObject(scroll); scroll.contentItem = obj } } } //Dummy.qml import QtQuick 2.6 Image { id: image; source: "http://placehold.it/650x650&text=\"Qt\"" }

@Mark81
I'm certainly not a D-Bus guru, my experience with it is somewhat limited. That said, I think QDBusReply::value can be used, provided you have registered your types.

Kind regards.

@Elg1
I don't think anyone/the OP is around any longer to answer from a thread from 5 years ago! Suggest you open your own new thread question.

@p3c0 I tried but that didn't work. Folks on Stack Overflow don't know either. I got no other choice :
https://bugreports.qt.io/browse/QTBUG-47407

@SGaist
Yes, It worked me out.

@ealione
The good thing is that typically users do not notice. The problem is popping up when trying to compile with older compilers or you remember that such stuff was not possible in the past.
As @mcosta suggests there is probably a recommendation out. On the other compiler versions are changing too rapidly and also the versions of recommendations.