[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.
Have you seen the photoviewer demo (in demos/declarative/photoviewer)? It uses the following techniques, which should be relevant to what you are trying to accomplish:
multiple layers of Views within delegates
packages, which allow smooth transitions of items from one view to another
For example, you might have an empty PathView of a single point sitting in the corner, which gets filled with the contents of the original circle PathView when transitioning to the next circle PathView. Packages can sometimes be hard to get started with, so I'd suggest also looking at the simple example in examples/declarative/modelviews/package.
width : 40
If you launch qmlviewer with -opengl it's perfectly smooth ... If you do the same with an animation you have a jerky movement .... I don't know if the only way is to hack qt to change the 16 ms timer resolution ?
Hmm, you are right, it is more complicated if you want clicking the empty space within the grid to deselect. I've edited anselmolsm's example to show one way to support this, along with a note on why the fix works. Note that the fix uses an undocumented property (flickableChildren) in order to have the MouseArea become a child of the contentItem.
If i found time, i'll help you. But actually it's just for fun. It's to study qml and i'm not sure canvas api interest people. Anymore, i write another plugin with another approach with a begin of webGl api support.
I think it's better to develop different approach and merge later.
[quote author="chetankjain" date="1283405899"]not sure eraseRect can help here, you will have to repaint that rect from the original image, there may be accuracy issue as tskd has already tried[/quote]
Right, good point. I was assuming the image was just a plain white fill. Thanks for the clarification.
If these things are working correctly with other (e.g. webkit) xmlhttprequest implementations, then it is likely a bug in the QML implementation. Is it possible to provide an example or specific instructions to reproduce in the "bugtracker":http://bugreports.qt.nokia.com, so we can further track this down?
That said, you should still be able to code application logic in script -- see for example the samegame or calculator demos in which all of the logic is implemented in script. The script will need to be coded in a "QML friendly" way though; for example you'll need to use the "dynamic object management":http://doc.qt.nokia.com/4.7-snapshot/qdeclarativedynamicobjects.html functionality provided by QML.
[quote author="mario" date="1280820453"]@mbasser: What version of Qt are you using? I can't make it work on the beta 1 release. Well, maybe it's time to update to beta 2 anyway.
I'm using HEAD of the qt-qml staging branch. contentItem was introduced in change 9d6ccfea89ae99b747f70ece71185868f189d0f9 (June 24) -- I'm not sure if it is in beta2; if not it will definitely be in the next release candidate.
Disabled Categories are greyed out
This topic will be moved to the category
Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.