Are you looking for blueRectangle to initially be positioned at rectRectangle.x + 120, but not bound to it? (so changing redRectangle.x does not cause blueRectangle to move?) In that case you could either use an absolute value for the position of blueRectangle, or assign a value to blueRectangle.x at component completion:
// this assigns a value, and does not establish a binding
Component.onCompleted: blueRectangle.x = redRectangle.x+120 @
[quote author="Gary_" date="1287690827"]It is the exact way I wish to access my model. However, it uses private classes/headers to achieve this. I assume it is so they can be flexible with the engine logic without impacting the public SDK.[/quote]
When 4.8 is released, the plan is that you will be able to continue using old import statements, or switch to new import statements if you want to use any of the new features provided.
The reason QtQuick 1.0 was introduced was to decouple QML versioning from Qt versioning. That will hopefully allow us to add new properties, etc within a minor release (e.g. 4.7), rather than having to wait for the next minor release (e.g. 4.8). This flexibility is important because QML is a new technology -- I think its natural that it grows at a different rate from Qt as a whole, which is overall quite mature.
A mouse up/down can be used in the following code to increment/dec the text value when the cursor is over top the item. What is the best way to make the scroll wheel do the same? Note, I need this for many items on a single screen. With a QDeclarativeItem subclass, would I need to implement the below in C++?
With the "implement in mainWindow and sync with qml", would this approach work and how does it look from a high level?
I'm still climbing the QML learning curve, so so looking for a high level overview or a place to start.
property color default_color: "white"
property alias text: text.text
property alias text_color: text.color
property int default_pixel_size
Working with a direct QObject-derived subclass rather than a QDeclarativeItem-derived subclass shouldn't be a problem (the engine itself knows nothing about QDeclarativeItem; to the engine QDeclarativeItem is simply another QObject with properties). Note that QDeclarativeParserStatus is an interface that is meant to be multiply inherited from (i.e. you would inherit from both QObject and QDeclarativeParserStatus to use it).
Qt Components is in an, let's say, alpha stage. If you get interested, in the repository pointed by danilocesar you'll find in the master branch a widget set for MeeGo (in progress). Also, check the branch mx, where you can see a widget set created in QML with the look and feel of the "MX toolkit":http://www.ohloh.net/p/mx-toolkit.
Ultimately almost all of the painting in the QML graphical elements is cached into pixmaps for performance reasons. This is done in the elements themselves (have a look at QDeclarativeRectangle::generateBorderedRect(), for example), so I can't think of an easy way to get around this without hacking all of the elements, or writing your own set of vector-based elements.
yes the value in myDelegate will be undefined.A solution to this problem is to reset the variable in myDelegate to NULL whenever the list starts moving( onMovementStarted: ) just to make sure it doesn't point to an invalid object/delegate
Do you have a ".qmlproject" file in your project directory? It has a QmlFiles field where it instructs Qt Creator where to find qml files. If you don't have one, it's possible that it's causing the need to reopen the project in order to load the new files, because, like Schneidi said, normally reopening is not necessary.
Hey guys, your are so great this actually solves the problem at the first sight.
before calling the QApplication constructor.
Now I get a pretty good performance on my Quad processor maybe I have validate this on
a weaker system, but I guess this should solve the performance problems we had.
Thanks mbrasser I already knew this page but I just forgot to consult this one ^^
[quote author="Thorbjørn Lindeijer" date="1285697851"]We've been reluctant to add additional primitives because of speed concerns. For example I wrote an Ellipse element, but it was not accepted since there is no way to make it fast.
However, there is a project that will allow arbitrary things to be drawn into a QML scene, emulating the HTML5 canvas rendering API:
You can do a lot of cool things with some imperative drawing code, but you should also be able to write a simple Line component in pure QML based on that.[/quote]
Ah, thank you for the response.