QML and Qt Quick

Modifying code in qgesturemanager.cpp function deliverEvents allows the gesture event to be delivered. The new code is invoked if existing methods produce a NULL target widget. The search only operates on gestures that have a hot spot. The search looks at all widgets for the best target widget that contains the hot spot. After that modification a target widget is found in deliverEvents and the gesture events that previously were not being delivered are processed. Not ideal to search all widgets, but its better than leaving the target widget null and eating a perfectly good gesture event.

you can get it from here. git://gitorious.org/qtify/qtify.git its a playground project by qt devs to show the power of qml

i know its pretty late, but i just stumbled upon colibri and i had (as rodrigob) quite a hard time to figure how to use clkeyboard together with a lineedit. But it is possible by letting the lineedit read the keyboard internal text. So basically the lineedit is just used to show a text which belongs to the keyboard itself! @CLLineEdit{ id: textInput text: keyboard.text } Rectangle{ height: 100 width: 200 color: "black" CLKeyboard{ id: keyboard anchors.fill: parent } } @

no, i mean else things. but thank you for your answer! i mean i want create dragdown notification panel. as it was made in ios and adroid- so it place for a clock, unanswered calls and news. i want make absolutelly as ios drag-down information panel by qml. it functional named Notification center. [quote author="shav" date="1365665589"]Hi, _dmp If I understand you correctly you want to fire some action when user is scrolling content to up or down, right? If this true, you may use signals for this. Qt is based on slot-signal technology. It's looks like iOS Notification centre. Please read more about signals from this "link":http://qt-project.org/forums/viewthread/1730 or "here":http://qt-project.org/doc/qt-5.0/qtqml/qtqml-cppintegration-interactqmlfromcpp.html. skiped -[/quote]

Hi, At least here it is stated that the callback should not be denifed before calling "open" https://developer.mozilla.org/en-US/docs/DOM/XMLHttpRequest#Properties

It is duplicated with https://bugreports.qt-project.org/browse/QTBUG-29686

I got some help from a couple of experts on IRC (#qt-qml) last night and my example is working now. I've answered the StackOverflow question that I linked to above if anyone is interested.

Not sure if you're still interested, but I had a conversation with a couple of former Trolltech employees on IRC last night. They helped me with this and I've posted the answer to my StackOverflow question.

This is exactly what http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-loader.html#using-a-loader-within-a-view-delegate tells about :) Moving the sub-delegate inside the parent delegate, or to a separate file, should make it work. With the Desktop Components example that was mentioned, it should be the same.

[quote author="amund_l" date="1364392619"]Included in QtCreator 2.7 is the "OpenGL under QML":http://qt-project.org/doc/qt-5.0/qtquick/quick-scenegraph-openglunderqml.html. This might be what you are looking for. It let you explore the new feature where QML is redered on top of your OpenGL ES context, so you can merge your OpenGL and QtQuick UI. Pretty cool.[/quote] Well...apart from perspective, rotating in more then one direction, an ambitious model loader that calculates matrices like Jackson Pollock before it hands over to QGLAbstract scene which is even more liberal... Yeah....Polys are for chumps :) https://www.shadertoy.com/

I got it, guys. When we set @width: rect.width * 0.5;@ is happening a binding. Not an assignment. What I should do to assign the value: @Component.onCompleted: { width = rect.width * 0.5; }@

In the future perhaps, hopefully, for 5.0 and 5.0.1 doc building failed for me (and not just me) and only HTML docs were generated, and worse than the online version - the missing snippets are still missing, plus there is entire articles that are missing too.

Hi All, everything works fine in 5.1! Thanks everybody. If somebody need help please let me know...

Ah, sorry for not being clear about my intentions. I'm trying to build an app using Ubuntu's new QML-based SDK, which has developers building app in pure QML. An example can be found "here":http://developer.ubuntu.com/resources/app-developer-cookbook/mobile/currency-converter-phone-app/. I'd like to build an app that interfaces with a third-party API, and I'd like to build that particular piece of functionality into a separate library.

Thank you for your input Chris, the point about this post, as hinted in the title, is to pass information from the place where the Loader Element is used to instantiate an arbitrary object, to the created object. The information passed, serves no deeper purpose then to be passed. It seems I've chosen a confusing example. Sorry about that. Maybe this will clarify: main.qml @import QtQuick 2.0 Rectangle { width: 360; height: 360 color: "aliceblue" Rectangle { anchors.centerIn: parent width: 300; height: 300 border {color: "black"; width: 1 } Container { anchors.margins: 1 aThing: Rectangle { width: 200; height: 200; border {color: "black"; width: 1 } Text { anchors.fill: parent; anchors.margins: 3; text: passedInformation wrapMode: Text.WordWrap } } } } } @ Container.qml: @import QtQuick 2.0 Rectangle { id: root property Component aThing: Item { } anchors.fill: parent color: "lightsteelblue" Loader { property string passedInformation: "some arbitrary information" anchors.centerIn: parent sourceComponent: aThing } } @

Okay i solved the problem, see this for an explanation i wrote regarding it (applies to qt quick 1 / qt 4.8 at the time). [quote]There appears to be a problem in Qt when trying to bind to model data that you are unsure the existence of. When binding normally, such as name: model.data , if model.data is undefined then the ‘name’ property will be overwritten with ‘undefined’, as opposed to not being bound to, where it would be free to supply its own default value / logic. A way around this is to use a Binding element, for example: @Binding { target: tempButton property: "displayString" value: model.displayString when: true }@ For some reason, even if you specify to always bind (like in the example above – when: true), an undefined value will not be bound. This is almost what you might expect as default binding behavior but is inconsistent with the previous method, where the property would get bound to undefined data. Even with the ‘when’ omitted, it is still more awkward (and potentially slower?) to bind in this way, as you have to specify an id for the object that will be the target of the binding. You cannot just specify the Binding element’s parent as a target, as this doesn’t appear to work for some reason – you have to specifically give the target an id.[/quote]