QML and Qt Quick

What do you mean by button? qt-components buton or button developed by yourself? In second case it will be good to post code here.

There's the "Basic Layouts Example":http://doc.trolltech.com/latest/layouts-basiclayouts.html and the "Flow Layout Example":http://doc.trolltech.com/latest/layouts-flowlayout.html.

There is no elide mode to provide this. You'll have to implement this yourself.

Does any know how can mouse event routed into widget?

I have found the solution to my problem and I hope this could help also the latest problem that has been posted. Basically the main mistake I did was to create a new QDeclarativeView when registering my models. Instead I had to use the QDeclarativeView I created in the main since it was the wrapper of my GUI. After that I wrapped in C++ the creation of my models in a class called ModelManager and I made it available in QML by calling setContextProperty. ModelManager has also a Q_INVOKABLE (or a slot. This is fundamental if you want your QML code to be able to called C++ methods) function "QVariant model(int index)", that gets the name of the model that was registered using setContextProperty and then returns the value of the model by calling QDeclarativeContext::contextProperty. Here is the code @ QVariant ModelManager::model(int pos) { Q_ASSERT(pos < m_models->count()); QDeclarativeContext* ctxt = m_view.rootContext(); QString name = m_models->at(pos)->name().toUtf8(); return ctxt->contextProperty(name); } @ Tks Maurizio Edit: Please use @ tags around code sections; Andre

Sorry, my mistake - I meant to write, it does indeed change to "bar" instead of "foo". This is the code that I'm trying: SomeItem.qml @ import QtQuick 1.0 Item { property alias product: m_product Text { text: m_product.productName } Item { id: m_product property string productName: "foo" } } @ main.qml @ import QtQuick 1.0 Item { width: 400; height: 400 Loader { id: select_loader } Component.onCompleted: loadDetailScreen("SomeItem.qml") function loadDetailScreen(source) { console.log(source); select_loader.source = source; //load the qml file shown above if(select_loader.status == Loader.Ready) { select_loader.item.product.productName = "bar"; } console.log(select_loader.item.product.productName); //that actually shows "bar" } } @

Also it will be good to add [solved] to title. Manually of course

That's a good idea. I went for an even cleaner approach now by binding the "state" of the object which I try to animate to a Q_PROPERTY in the C++ interface. The different states are linked to transitions (in QML) which do the animation I want.

Looks like it's working pretty good. I wonder if the Loader has some kind of cache under the hood to maximize performance. Thanks.

Ups, sorry, missed the forum topic. Just saw WebView :-)

This question raise a design issue; while is not a very good idea to pollute your root object with tons of functions, is still a good idea to put to root object all the function you need. You should try to think about root object as the interface to your qml gui: the deep you go through your QmlItems the wrost is going to be. You should expose a clear interface on your root object so changes behind the scenes can be kept hidden. In your case you should write a search function on the root object that parametrically finds what you want; that function should be semantc: say what you want and i will give it to you. Once again changing the entire qml and providing the same interface, gives you a new way to present and do stuffs, without change the backend. Doing so, you may see you are going to write too much function on your root object. In this case you can consider to write some interface Item on your Qml code directly behind your root object. So you can broke down interfaces by semantically unrelated groups and provide those interfaces as main gateways through your root object. I hope this can clear your picture.

Hi Guys, Thanks for your help, I have moc and I have added @ HEADERS += myclass.h SOURCES += main.cpp myclass.cpp @ in my .pro file. I found my mistake, I must also add @ CONFIG += qt @ It works now, even though I don't know why. =)

[quote author="mario" date="1305789703"]Oh, I haven't tried the library myself so I have no clue on how to use it. Try contacting the authors (there's a contact page on the site). I think they will be glad to answer your question. [/quote] Ok, thanks.

Items in external component files are limited in scope to their own file. If you wish to expose properties of internal items in a component then you need to define alias properties in the top-level item of the component. See this "article":http://developer.qt.nokia.com/wiki/QML_Progress_Spinner for an example.

Donner: I got your point. The normal way is, you can specify a property to binding with the State. @ State { name: "C" when: menuPage.x == STATE_B_POSITION_X PropertyChanges { target: menuPage x: STATE_C_POSITION_X ... ... } }@ It will have a warning "<Unknown File>: QML StateGroup: Can't apply a state change as part of a state definition.", but you can ignore it.

I do not know the example. I just reasoned backwards from the chunk of code you posted.

Yeah, I did say "not tested". Thanks for pointing out my (ahem) deliberate mistake ;-)

Maybe you could raise brightness & contrast levels... It would be more effective (and impossible, I think) to raise screen's voltage level XD. --