QML and Qt Quick

You have onWidthChanged / onHeightChanged slots in QML and widthChanged / heightChanged signals in C++. But I'm not sure this is what you're searching for.

Little correction : when looking at the strings in console, new lines do not appear but if I copy-paste the content of the console and put it in an editor like Notepad++ they do appear as "CR LF". Looks like it isn't as trivial as I thought if no one can help... Should I report a bug, seems like I'm not the only one that encountered this issue : http://www.qtcentre.org/threads/44314-a-way-to-display-xml-node-value-with-new-line-(-lt-br-gt-) EDIT : putting the text in the XML file in <![CDATA[ TEXT<br/>TEXT]]> worked

I have it working now. The problem was with the way I installed OpenSSL as discussed in this "thread":http://qt-project.org/forums/viewthread/25799/ Thanks to everyone who contributed suggestions!

Nothing. It is simply a convention to make it clear to the user that these properties are not part of the public API and should not be used in third party software. In principle yes. But there are no guarantees that those properties will exist in a future Qt release or keep the same behaviour. If you make use of those properties, your code might stop working with a future Qt release. Not really. More recent versions of Qt Creator might hide them from code completion or code browsing and qdoc will skip those properties while generating documentation. Aside from that they are just regular properties. It doesn't. We were discussing the possibility of introducing private property scopes at the Qt Contributors Summit this week but there are currently no concrete plans. Regardless, just like in C++, we will always need to declare some public functions that we want to keep outside of the public API.

Can you post the full message? Assertions from microsoft libraries can somtimes be "ignored". Does the program continue after that?

button and label are defined as components and not items. In practice it means that you cannot "see" them in the same scope like you are assuming here. A simple solution is to animate this without using state: @ import QtQuick 2.1 import QtQuick.Controls 1.0 import QtQuick.Controls.Styles 1.0 ApplicationWindow{ id:win Rectangle { Button { id: btn1 text: "A button" style: ButtonStyle { background: Rectangle { id: btnBackground implicitWidth: 100 implicitHeight: 25 border.width: control.activeFocus ? 2 : 1 border.color: control.hovered? "red" : "white" color: control.hovered? "white" : "red" Behavior on border.color { ColorAnimation{ duration: 400 easing.type: Easing.InOutQuad } } Behavior on color { ColorAnimation { duration: 400 easing.type:Easing.InOutQuad } } radius: 4 } label: Text { id: btnText text: btn1.text color: control.hovered? "red" : "white" Behavior on color { ColorAnimation{ duration: 400 easing.type: Easing.InOutQuad } } horizontalAlignment: Text.AlignHCenter } } } } } @

[quote author="sierdzio" date="1374129274"] The plan is to release it around late November this year. There may be some delays as usual. I would say you can expect it to be released somewhere in December/ January.[/quote] Thanks, I would expect a beta or RC version on November this year. [quote author="realtebo" date="1374131288"]:) and so like in other project, what could be adopted by 1M of people will be used only by 1k[/quote] I am not familiar with Qt on android by now, but if you want to deploy your apps on mac, or just want to compile or run your programs on windows, I could give you some help. The prebuild binaries of Qt5.1 are complete SDK, that means you could just open the QtCreator and begin your development, the compiler and proper Qt version should ready for you to play with.Just choose the category of project you want to build.If you want better control, you could study how to edit your .pro. .pro is some sort of file which told qmake "what kind of make file I need?".qmake is a makefile generator like cmake, both of them could cross platform, qmake can generate .moc for you, which needed by those QObject(I don't know cmake could generate it or not). Please tell us which desktop you want to give it a try?windows, mac, linux? There are many packages for windows, you could categorize them like this 1 : there are two kind of compilers--mingw and vc series 2 : 32bits and 64bits 3 : angle or opengl(mingw do not have angle version yet, weird) angle is a wrapper to translate the opengl api to directX api for the windows users. "Angle or opengl?":http://qt-project.org/wiki/Qt-5-on-Windows-ANGLE-and-OpenGL

I found a solution: To stop flicking when use a pinch gesture, mouse events inside a child component of a flick page you have to set the flickable's property "interactive" to false. Then the pinch/mouse events are propagated to underlaying childs. To get key input you have to set Flickable's focus to true. Note: In my case I use a QGraphicsProxyWidget to embed a custom QGraphicsView/Scene into QML. The propagated events from QML to that widget seems to finished at QGraphicsProxyWidget's handler. From that point it's your task to deliver events further. To set focus of Flickable and change it's property interactive I emit my defined signals interactiveFlick(bool) and focusFlick(bool) from inside QGraphicsProxyWidget::sceneEvent().

see http://qt-project.org/forums/viewthread/30007/

p

Nope, just set it to false and you'll get the rectangle's background.

push

Thanks, syntax or not:-) I need a way to detect such errors. You are right, with @ height: myValue @ I get a ReferenceError: myValue is not defined message, which is very helpfull. But not for the line @ height: parent.heightt @ I see no reason to ignore the second one except a bug. Best Steffen