QML and Qt Quick

This code is used for all platforms using the MouseArea QML item, probably you meant the initial sending of MouseEvents themselves? In this case the (platform-specific) QApplication class would probably be a place to look for (at least it's the case for Win, s60, ...). Alex

This works for me, both QtQuick 1 and 2: @ Flickable { id: root width: 200; height: 200 contentHeight: 600 pressDelay: 500 Rectangle { width: 50; height: 50 color: ma.pressed ? "blue" : "green" MouseArea { id: ma anchors.fill: parent } } } @

This is a bug. I've filed QTBUG-26290 to track this issue.

See http://qt-project.org/wiki/QtDesktopComponents instead.

Yes, the typed version is definitely better in my opinion too. I'd say that you're right, and that QTBUG-15641 is related (although I can't remember enough of the QtQuick1.x code to say why the cached typedata resolution could fail for inline components, or how that might be reproduced in your use-case). Unfortunately, we're focusing purely on Qt 5 at the moment, and that bug in QtQuick1.x is unlikely to get fixed soon. Another possibility is to use "property QtObject propname", instead of "property variant propname" -- at least then you get the typechecking for QObject-derivedness, so attempting to assign integers or strings etc will fail. It's not perfect, but it's better than nothing, I guess. Cheers, Chris.

Thanks for answering my question. I also found template files that can be updated in QtCreator/share/qtcreator/templates/qtquickapp/qml/

hi thanks but it's still unclear for me : I have those depencies in ${package}_template.pkg but not ${package}_installer.pkg @ grep -i components *.pkg redak_installer.pkg:; Dependency to Symbian Qt Quick components redak_installer.pkg:; Default dependency to Qt Quick Components for Symbian library redak_stub.pkg:; Dependency to Symbian Qt Quick components redak_stub.pkg:; Default dependency to Qt Quick Components for Symbian library redak_template.pkg:; Dependency to Symbian Qt Quick components redak_template.pkg:(0x200346DE), 1, 0, 0, {"Qt Quick components"} redak_template.pkg:; Default dependency to Qt Quick Components for Symbian library redak_template.pkg:(0x200346DE), 1, 1, 0, {"Qt Quick components for Symbian"} @ More infos : https://bugreports.qt-project.org/browse/QTCREATORBUG-6338 https://bugreports.qt-project.org/browse/QTSDK-1283?focusedCommentId=180330#comment-180330 -- http:/rzr.online.fr/q/symbian

OK... thanks

Have you tried explicitly setting accepted to false? I don't know if that would work, but logically it should... Glad you got it figured out, though. :) I know the feeling; I spent hours trying to figure out how I could make a scrolling ListView not show list items that have scrolled outside of the view, and finally found that wonderful clip property. Pfft. :)

Probably you need to use OS-specific APIs... or test with Qt5 - there might have been a change there (definitely was for mouse buttons).

Hi, The issue in this case is that Loader loads the QML on the main thread (effectively blocking it), which the Timer is also running on. This has been addressed in QtQuick 2.0 via the asynchronous property added to Loader (which allows animations to run while the loading happens). Regards, Michael

Of course. You should to talk about it in QtonPI group.

Solved this myself. The problem was that I had defined QT_NO_CODECS and QT_NO_TEXTCODEC when configuring Qt. If I remove these definitions, things work as expected (except for a bug which I have reported as "QTBUG-26193":https://bugreports.qt-project.org/browse/QTBUG-26193).

I think these properties screenHeight and screenWidth need to go away. They make no sense; they seem to be copies of width and height. Looking at your code there, this is the only code I see that actually seems useful: @ Rectangle { id: root Rectangle { //Whatever actually goes in this thing } } @ From the C++, you can just set the root object to resize to the view like I showed earlier, do a viewer.showFullScreen() and be happy. :) Oh, and stop using Component.onCompleted() to tell you what the sizes of things are. QML doesn't work that way -- components are completed, but after that changes continue propagating through until everything is set up the way it's supposed to be. Rendering a QML GUI is a multistep process that happens behind the scenes, don't expect onCompleted to have the final values of things. It will have the initial placeholders (most likely 0) that are used until everything is created and real values can be calculated. Of course, my response is naive because I don't know what you're actually trying to put on the screen. If I had some idea of what you want your window to look like, I could give much more useful responses.

QML file is UTF-8, C++ files are Latin-1. Filed a bug report for this as "QTBUG-26193":https://bugreports.qt-project.org/browse/QTBUG-26193.

yes, it was my mistake that i didn't checked the details. by specifying "radix", one can force parseInt for conversion...