QML and Qt Quick

Hi and welcome to devnet, You should add what OS/Qt version you are running and which board your using

solved it by handling from model. added new role (bool) to display text or image.

Thank you for your answer!!! You suggestion does not work for me. I'm using Qt 5.3.2. And I've found another way to fix it) The problem was caused in [code] flickable.contentHeight - flickable.height [/code] As my flickable element that is passed to the scrollbar is a child element of Item with its own height and width, I made an additional [code] property int flick_width; [/code] in my ScrollBar.qml. So I've just replaced flickable.height by flick_width.

Dear JKSH! Thanks for your advice! I did the same for now and it works. I develop some application framework, and it is good for me to catch this signal directly, because in other way I have to ask users to implement that custom signal. In my situation, we control the base object, "MyWindow". So I put that custom signal there. It looks almost same as onCompleted in MyWindow user's descendant.

You're welcome ! That's what Qt does ;) Since you have it working now, please update the thread title prepending [solved] so other forum users may know a solution has been found :)

I just found the way to do it thanks to a new feature of Qt 5.4 : QtQuick.TextMetrics element With TextMetrics::tightBoundingRect property we can get the same bounding box that Photoshop is based on and with TextMetrics::boundingRect property we get the bounding box that Qt use to position the Text element. With these two informations we can now compute the right horizontal & vertical offset we need to match exactly the position on Photoshop. To encapsulate the conversion we can create a custom Qml Component based on QtQuick.Text for instance: @<PhotoshopText.qml> import QtQuick 2.4 Text { id: root property real xPS: 0 property real yPS: 0 // convert from Photoshop coordinates to Qt coordinates x: xPS - textMetrics.tightBoundingRect.x y: yPS - (textMetrics.tightBoundingRect.y - textMetrics.boundingRect.y) TextMetrics { id: textMetrics font: root.font text: root.text } } @ Now we can use this new component to position any text with Photoshop coordinates: @<main.qml> import QtQuick 2.4 Item { PhotoshopText { text: "Hello world!" xPS : <x value extracted from Photoshop> yPS : <y value extracted from Photoshop> } } @ Thanks @Juergen for your help on this issue, you put me into the right direction ;) I can now finalize my PSD => QML converter :D Best regards Krys

i got it, thank you a lot :-)

Are you trying to create the GUI in QML and asking what you use instead of a QLabel? In QML you could just use a Text object for a label. It's hard to know exactly what you're doing when you say "move a class ... to Qt QML". If you're new to QML you might benefit from my my latest Pluralsight course on "Qt Quick Fundamentals":bit.ly/qtquickfun on Pluralsight. Pluralsight is a subscription service but if you send me an email through the forum I can give you a free week long VIP pass good for unlimited hours of watching, including offline.

+1 Jens for the exact solution.

What worries me is the fact the echo() slot is never triggered. Not even as the application is closed. This leads me to believe such objects returned to QML are practically leaking, and I am not a big fan of believing somehow this is not the case. I don't like memory leaks. And somehow QML seems to be full of those. I've already encountered situations where QML doesn't release resources and memory usage climbs to hundreds of MB and never drops down.

Hi, I can not reproduce your issue. Could you elaborate little bit more. It would be perfect if you could show the exact code that shows the problem. @ Item { x: 200 y: 200 width: 200 height: 200 scale: 2 Rectangle { border.color: "black" border.width: 2 anchors.fill: parent } Rectangle { id: item1 x: 10 width: 5 height: 100 color: "red" Rectangle { x: /*item1.x +*/ item1.width width: 5 color: "green" height: 100 } } } @ This didn't show any gaps. Do you have rotations on your items and/or are they Images?

I marked the tread as SOLVED, as the problem is now understand. Would still be interesting to know if this behavior s intended or not, might be the Mailing List will answer this.

Unfortunately creating a sample application won't be possible because the application is quite complex. For now I am using a sleep() just before showing the application.

Problem is finaly solved!

[quote author="chriadam" date="1332833133"]QML already does this. A QObject which is returned to QML from an invokable function as a return value has its ownership semantics set to JavaScriptOwnership if it has not previously been explicitly set to CppOwnership. [/quote] How does this work considering QObject can't be returned by value?

To summarize: The compiler adds the option of letting you compile QML and javascript into efficient C++ code, giving you the option of more effectively hiding/obfuscating your QML in commercial applications and improving the initial startup time of QML applications as it takes away the compilation step at runtime. It does not affect what is currently available in the open source edition.