QML and Qt Quick

Yes, as far as I know GridMesh only defines a resolution, and is meant to be used with a custom vertex shader.

You know that instead of adding new clas you could use QPointF: @ //.h file class Map : public QObject { Q_OBJECT Q_PROPERTY(QPointF center READ getCenter NOTIFY centerChanged) public: explicit Map(QObject *parent = 0); inline QPointF getCenter() const; void setCenter(const QPointF& aCenter); signals: void centerChanged(); public slots: void blabla(); private: QPointF m_center; }; QPointF Map::getCenter() const { return m_center; } //.cpp file void Map::setCenter(const QPointF &aCenter) { if (aCenter == m_center) return; m_center = aCenter; emit centerChanged(); } //Part of qml file Connections { target: myMap onCenterChanged: { myTxt.text = "x " + myMap.center.x + " y " + myMap.center.y } } @ If you want to use longitude and latitude keywords you can do: @ //.h file Q_PROPERTY(QVariant center READ getCenter NOTIFY centerChanged) //... QVariant getCenter() const; //.cpp file QVariant Map::getCenter() const { QMap<QString, QVariant> centerMap; centerMap.insert("longitude",m_center.x()); centerMap.insert("latitude",m_center.y()); return centerMap; } //.qml file Connections { target: myMap onCenterChanged: { myTxt.text = "x " + myMap.center.longitude + " y " + myMap.center.latitude } } @

Hi, This problem was mentioned in "this":http://qt-project.org/forums/viewthread/9897/ post

Hi, The CDATA wrapper itself should be automatically removed by XmlListModel (i.e. the beginning <![CDATA[ and ending ]]> should be stripped off). The link at the beginning is part of the body of the CDATA, so if you want to remove it you'll need to do so via string manipulation (e.g. rssDescription.substr(rssDescription.indexOf("<p>")) ). Regards, Michael

Hi, QtQuick 2.0 introduces a Canvas element that might be useful for this. Another option might be creating a custom item for drawing the curve (there are no built-in curve drawing items, besides the newly added Canvas). Regards, Michael

Hi, You should be able to get this working by changing the first line to: @var str = url.toString()@ Regards, Michael

Thanks a lot DigitalPioneer.. it worked..Thank you very much!!! :)

Bug it's only under MSVC. Solution: work with MinGW

Anybody has a suggestion? I have the same problem on my arm 300 mhz device... I also want to drop the scroll animation and just jump immediately to the next item.

[quote author="bkamps" date="1339785531"]Too bad QtQuick doesn't offer some handy stuff to do something simple like showing a wait dialog... [/quote] Well, with QML still being relatively new, you will have to wait for it (pun very much intended :P). Right now QML consists mostly of the basic building blocks. You are free to take it anywhere, but you have to do the "taking" yourself. Or look into some material from other people, like the desktop components, etc. Over time number of available components and add-ons will grow (if there is enough interest in QML).

So it happens i was using the same path for both simulator and device, which is not correct. I can access the database with: @#ifdef Q_WS_SIMULATOR viewer.engine()->setOfflineStoragePath(<PATH>); #else QString privatePathQt(QApplication::applicationDirPath()); QString pathOfflineStorage(privatePathQt); pathOfflineStorage.append(QDir::separator()).append(<PATH>); pathOfflineStorage = QDir::toNativeSeparators(pathOfflineStorage); viewer.engine()->setOfflineStoragePath(pathOfflineStorage); #endif@ Now i can access it but i can't edit it permanently. I run it in the simulator, make some changes in a table and when i restart it the changes are not saved.

Haven't used the QmlApplicationViewer, so I don't know how to do that, sorry. I assume you would have to change the QmlApplicationViewer source code, where the declarative view is created. Just create a QGlWidget, and set it as the declarative view's viewport. You may also have to adjust its QGlFormat to something suitable for your device.

Well i gave that a try and works perfect thanks for your help

But i had seen that there are many APIs in QML that can be used in place of C++ . Somthing like Qt Mobility etc. etc.

qmlEngine and QDeclarativeEngine::contextForObject returns NULL in class A constructor. I've done creating additional internal components in A::onCompleted - there i can get pointer to engine from qmlEngine function.