QML and Qt Quick

If you're talking about their visual appearance, why not set visible to false? That should stop them from taking up any space in the visual layout. But that's a separate issue to the object lifetimes. Why is it important that you delete some before creating others? Are you on a really tight memory budget, or something? Cheers, Chris.

yes, I found "this":http://doc-snapshot.qt-project.org/qt5-stable/qtgraphicaleffects/qml-qtgraphicaleffects1-rectangularglow.html for Rectangle glow. But I dnt know why it is making the corners rounded with out my consent. Guess it is due to the default cornerRadius property [quote author="inblueswithu" date="1378148099"]I dnt know why this glow is not applying for a Rectangle element. Here is the code: http://pastebin.com/PL4dWWdM Any help?[/quote]

This is qt-components code not official Qt code?

I am aware of the import statement from QML. However, my plugin has no QML component; it is C++ only. So what I'm asking is how to achieve the effect of "import B" in C++. Burk.

I am using the QtQuick desktop components : http://doc-snapshot.qt-project.org/qt5-stable/qtquickcontrols/qtquickcontrols-index.html bye andruj

up !

Qt Help (in Qt Creator) -> Look for AnchorAnimation -> Detailed Description, Note...

Hello, Actually I didn't use QtQuick controls especially, but QtQuick elements (like Rectangle, MouseArea, etc. ) and all what I needed to do is to go to project properties, under "Run" options, and then "Package configurations", and check the "Qt5Quick" library in the "Required Qt libraries" field. It is working well both on emulator and on the device (Galaxy S3). It's also important to target the good Android version in the option "Android Target SDK". First time I compiled with API17, when my phone was only at version 4.1 of Android (API 16), so it was not working. About BlackBerry I don't know... Never used.. Hope this help

There is a contradiction in your webcontainer item. You say that the content height of your flickable is equal to the web_view height. And you say that the web_view height is equal to the webcontainer height. The only way to interpret this is that the flickable contentArea has the same height as its parent which should in exactly the behaviour you describe. I suspect it will work if you don't explicitly override the preferred height of the web_view

I'll take a look at it. Thank you.

hello as it seems it was solved in this release 5.1.1 thank's for help, andruj

Sure, manually emitting the signal is a good way to ensure that appropriate signal handlers and bindings get evaluated after a change (indeed, this is what you have to do in C++ if you're handling property modifications manually). Probably best to wrap the push/pop+signalEmission into helper functions, for convenience. Cheers, Chris.

Yes @LIBS += -lyour_library_name -Lpath_to_your_library@