QML and Qt Quick

First, you need to ask questions which are (a) more precise, (b) more detailed, (c) less vague. What do you trying to achieve? What have you tried so far? What went wrong? Is there any information you can provide (such as error messages which were returned) which might provide some clue as to what went wrong? Second, you need to read the documentation. The documentation (in particular the Qt Quick Application Developer's Guide) contains a lot of information which should be useful to get developers up and running quickly. I'm not going to link you to it directly, as I think you should be able to find it on your own with a couple of minutes Googling or searching these forums (as I have posted the link here multiple times), if you find the Qt Project documentation landing page too complex to navigate directly - as I admit that it can be confusing at first. Cheers, Chris.

Awesome! I started looking at the QStyleItem implementation but was not exactly sure what to look for. I modified the QStyleItem::paint implementation for the troubled components (CheckBox, RadioButton, and Button), where no widgets are passed when drawing the control: @qApp->style()->drawControl(QStyle::CE_CheckBox, m_styleoption, painter, NULL);@ Thanks again! This worked out very well with minimal code changes.

I have solved this problem, thanks. @ import QtQuick 2.1 Rectangle { id: container width: 360 height: 360 TextEdit{ id: textEdit text: "fasjkljklzvjjfopasdj09jropwejofjasdl" color: "red" } Item{ id: testItem anchors.fill: textEdit Component.onCompleted: { for(var i=0;i<textEdit.length;i++) { console.log(textEdit.positionToRectangle(i)); var object = Qt.createQmlObject("import QtQuick 2.0; Text{}",testItem); object.text = textEdit.text[i] object.x = textEdit.positionToRectangle(i).x } } } } @

I've been thinking, how hard is to implement the few basic primitives as QQuickItems with custom geometry and use them in declarative to create compound objects. The scenegraph will do the same work, objects are just gonna end up taking a bit more space in ram, but will have the advantage of being more flexible, dynamic and reusable. Just plug a shader in it to get a material and voila.

So, I writed an own declarative item and now works. svgitem.h: @#ifndef SVGIMAGE_H #define SVGIMAGE_H #include <QDeclarativeItem> class QGraphicsSvgItem; class SvgImage : public QDeclarativeItem { Q_OBJECT Q_PROPERTY( QString source READ source WRITE setSource NOTIFY sourceChanged ); Q_PROPERTY( QString elementId READ elementId WRITE setElementId NOTIFY elementIdChanged ); QString mSource; QString mElementId; QGraphicsSvgItem* mSvgItem; public: SvgImage( QDeclarativeItem *parent = 0 ); QString source(){ return mSource; } QString elementId(){ return mElementId; } void setSource( QString source ); void setElementId( QString elementId ); signals: void sourceChanged(); void elementIdChanged(); }; QML_DECLARE_TYPE( SvgImage ) #endif //SVGIMAGE_H @ svgitem.cpp: @#include <QSvgRenderer> #include <QGraphicsSvgItem> #include "svgimage.h" SvgImage::SvgImage( QDeclarativeItem *parent ) : QDeclarativeItem( parent ) { mSvgItem = new QGraphicsSvgItem( this ); } void SvgImage::setSource( QString source ) { mSource = source; mSvgItem->setSharedRenderer( new QSvgRenderer( mSource ) ); emit sourceChanged(); } void SvgImage::setElementId( QString elementId ) { mElementId = elementId; mSvgItem->setElementId( mElementId ); emit elementIdChanged(); } @ Use: @SvgImage{ id: deck source: "william-tell.svgz" elementId: "back" } @ And the tutorial "here":http://www.developer.nokia.com/Community/Wiki/Creating_a_custom_QML_element_with_Qt

I think you can use something like this: (I'm using this to load some QML model before the actual GUI loading, JSCode would be the same, I think.) @ QQmlEngine e; QQmlComponent global_object_component(&e, QUrl::fromLocalFile("global_object.qml"), QmlComponent::PreferSynchronous); QObject *global_object = global_object_component.create(); if (global_object) { e.rootContext()->setContextProperty("global_object", global_object); QQmlViewer view(e); view.setSource("GUI.qml"); view.show(); //at this point my QUI.qml can reference global_object } else { //error } @

damm, had the same problem. for the record, the error message was Invalid property assignment: "roles" is a read-only property where Q_PROPERTY(QQmlListProperty<ModelRole> roles READ roleObjects)

[quote author="njeisecke" date="1368618421"]Models should be part of the business logic and belong to C++. Accessing model data is currently readonly. You must provide a Q_INVOKABLE setData method in your model if you want to modify data in a C++ model. [/quote] Thank's so much for your response and detailed reply neisecke.

Yeah, I managed to make a draft of a the manager. Now my application is waiting for the database before creating the interface. Like you said, I'll need to have a splashcreen to display the downloading of the database as it may take some time... thanks a lot.

Yep you where right. It has to be in the qml folder not in the import folder. Thank you very much. :)

Cool :) Please prepend "[Solved]" to the topic's title (you need to edit your first post too do that), it might help some other bloke in need ;)

It sort of looks to me like I'm going to have to go through the whole business of putting a QComboBox into a QDeclarativeItem rather than a QGraphicsProxyWidget. If I've stumped the crowd here, I'm guessing that getting keyboard focus working with a QGraphicsProxyWidget would be hard.

Nobody has an idea? Workaround?

Thank you very much for your insightful response! I've fixed my code and removed the margins, etc. and everything is working much better now. I really appreciate your feedback!!! Now if I can only figure out how to find the width in pixels of the longest (widest) line of text contained within a ListModel, still trying to figure that one out, heh. :-)

Argh, thanks...didn't realise that they skipped the part where they explained the floodFill function. Guess it sometimes would be worth it to read the guide a bit more thoroughly. Once again Thank you!

Your are right. I have inserted the following line between line 16 and 17: @ canvas.unloadImage(canvas.path)@ Now it works.

Thanks:)