QML and Qt Quick

juddster!! thanks! that did the trick.. now on to the next problem lol :P thanks again!

Please do. I'm happy to know people learn from my code, just as I have learn a lot when I wrote it (that project has seen several heavy refactorings).

bq. Thanks! I guess you meant the MouseArea though, that’s the one that has the onReleased handler. Yes, exactly ;)

I published my third course on Qt this month. The final course is on "Integrating Qt Quick with C++":http://bit.ly/qtquickcpp. Watching it might save you some time. While it's probably not obvious from the table of contents interacting with the Canvas via a C++ class is covered in the 5th module "Registering C++ Types". It might be a little confusing to jump into the middle of the course but I still think you'll find it helpful. Of course I think you should watch the entire course but that's a little self-serving. Pluralsight is a subscription site but they have a free ten-day trial (limited to 4 hours) and I also have some VIP passes left. The VIP pass is good for a week but includes the ability to watch unlimited hours during the week, download the course materials, and watch offline (offline content will expire with the pass). If you want a pass, just send me an email through this forum.

Thank your for fixing the problem. That was just ignorance on my part

Hi, has this bin ever solved? I'm using Qt5.4 on VS2013 and it appears that my program is running in exactly the described issue with deleteLater. The code I use creates dynamic QML items which are stored as QQuickItem. As soon as they are not needed any longer they are scheduled to be destroyed using deleteLater(). Also as previously described in this thread setParent(nullptr) setParentItems(nullptr) doesn't make any difference. In my code this only happens if the QML has bindings to C++-External classes, which are definitively still alive and in well shape at the point the QuickItem gets destroyed. I know thread necromancy is not always a good think. So if it helps anybody I'll create a new thread. Thanks for your help Cheers Kieren

Hi! mouse.button holds the button that caused the event. So, positionChanged is not caused by any button, thus mouse.button is alway 0 in onPositionChanged. You need to check mouse.buttons. Note the plural s. It is mouse.buttons. mouse.buttons holds a bitwise combination of all buttons that were pressed when the event occured. @ onPositionChanged: { console.log(mouse.buttons) if (mouse.buttons & Qt.LeftButton) console.log("rotate") if (mouse.buttons & Qt.RightButton) console.log("zoom") } @ It's a bit tricky, but one gets used to it :-)

The issue is solved. Thanks for the support so far.

bq. I thought by setting the QObject parent of the dynamic object, Qt would clean it up properly. Yes, should. I don't understand why this is messed up. Maybe it is a bug in Qt. I give up on this for now. My final quick fix (Quick, haha...) : @ onParentChanged: { console.log("this:" + this); if (!hasOwnProperty("parent")) { return } if(parent != null) { validParent = true; } else { validParent = false; } console.log("parent: " + parent); } //onParentChanged @ Cheers

Yes of curse I am trying all examples related to the subject as we speak. Yet someone might have some better tutorial or learning material, you never know.

hi sletta, Thanks for your reply! Your explanation is very clear! My target platform is Android and iOS. I think it don't has any problem in iOS but not sure about Android. Is it safe to use multisampling on Android platform? I think the hard part of per-vertex antialising is to determine the no. of vertex should be added. Making triangle is just my first step. I need to make a lots of arrow and zoom-in is supported.

Indeed, it was only recently that I learned you are able to do that. Thanks for your help.

No I dint do that, how should I do it?

@onClicked: { m.image=imagesListModel[index]; main.source=m.imagesListModel[index] // console.log("User select '"+"' image"); }@ m is the Detectsquares object and i m setting the path and then assigning the path to the main image Here is the code im main.cpp: @ QApplication app(argc, argv); // QQmlEngine eng; QQmlApplicationEngine engine; engine.load(QUrl(QStringLiteral("qrc:/main.qml"))); DetectSquares m; engine.rootContext()->setContextProperty("m",&m); QQmlComponent component(&engine, QUrl::fromLocalFile("qrc:/main.qml")); component.create(); @

Sorry, no idea :-/

Does this work? Has anyone tried this using QT 5.4 and MFC? Please let me know. Thanks and regards, Karrtik