Well thank you very much !
I understand more about the consequences not putting it on the heap. Not using new is like not using a malloc in C... tell me if I'm wrong. Is it referring to lvalue too ?
Unfortunately not. At first I would say you should try to get the profiler up and running to find out where you actually need to improve performance.
If you still face problems in certain situations I would suggest to take the issues to the mailing list (development@qt-project.org).
[quote author="Julie1986" date="1348143386"]I need it in qml. not with Qt.[/quote]
Then you should have 1) explicitly have said that, and 2) posted in the right forum (I moved it now for you). Note that QML is also Qt.
It is just a little hack but to have the position for the video origin in the upper left corner use in qml:
@
QmlVideo {
id: videoID
x: -485
y: -350
}@
yes,, as you stated, when name is 'color' rather than 'bgColor',,,
@
color: color
@
will make binding loop, in this case, to avoid this situation,
you can write down 'model.color', without changing list model.
@
color: model.color
@
Guys, I ran into the same problem. I was trying to extend QDeclarativeItem with some properties, but then I cannot access anymore the "implicitWidth" and "implicitHeight" properties. More, state change seems not to be signaled either... Any idea? This is using Qt 4.8.1 on Linux.
Thx!
Thanks. SnapOneItem mode and orientation are already set and ListView flicks fine when delegate's Flickable has nothing to flick in it.
Will play with events, but at the monent I have no idea how to bind events between Flickable and parent ListView.