Re: [Interest] QML Listview delegate in C++

Den 05-06-2015 kl. 23:04 skrev Simone: > I'm facing a problem in my QML application. The target is an Arrm processor Ah, the pirate processor :) > (freescale iMX53) with not so much capabilities. > My problem is that I have a quite complex listview delegate item, and I > observe a cpu usage very

Re: [Interest] QML Listview delegate in C++

Hi Simone, It will help if you can describe your delegates, as in what Items are there in your delegate? It will be even better if you can paste the code here (at least the Item hierarchy in the delegate). Using that people can suggest optimizations. Cheers, On Sat, Jun 6, 2015 at 2:34 AM, Simon

Re: [Interest] Recent Qt5 does not compile with mingw64

Thiago, Kai: This is bad. No WINBOOL in the qt5 sources anywhere. Bad because if it is a MinGW problem, it is unlikely it will be fixed. And it is worse since it is the 'semi-official' MinGW, which is used in this wiki: https://wiki.qt.io/MinGW-64-bit MSYS2 method, MinGW-w64 I will play around

Re: [Interest] Python not found when building QT 5.4.x

On Thursday 04 June 2015 16:56:40 Olivier Barthelemy wrote: > I am launching QT5 build from sources, from a cygwin bash terminal on > windows. Don't use Cygwin, please. Either use the regular Windows prompt or use mingw / msys shells. -- Thiago Macieira - thiago.macieira (AT) intel.com Softwar

Re: [Interest] Recent Qt5 does not compile with mingw64

On Wednesday 03 June 2015 19:13:04 Guido Seifert wrote: > Ooookay... the QSharedMemory problem I can work around by not compiling the > examples: -no-compile-examples. But then much later I get: > > .moc/debug/moc_context3d_p.cpp:1935:16: error: 'WINBOOL' is not a member of > 'QtCanvas3D::CanvasCo

Re: [Interest] Memory leak in QML Image

Sorry guys, it seems that I'm wrong... 06.06.2015 0:41, Igor Mironchik пишет: Hi guys, If in QML I have propertyintcurrentValue Image{id:curr;source:""} onCurrentValueChanged:{ if(root.currentValue < 0 || root.currentValue > 9) root.currentValue = 0 cur

[Interest] Memory leak in QML Image

Hi guys, If in QML I have propertyintcurrentValue Image{id:curr;source:""} onCurrentValueChanged:{ if(root.currentValue < 0 || root.currentValue > 9) root.currentValue = 0 curr.source = "file:" + applicationDirPath + "/" + root.currentValue + "

[Interest] QML Listview delegate in C++

Dear All, I'm facing a problem in my QML application. The target is an Arrm processor (freescale iMX53) with not so much capabilities. My problem is that I have a quite complex listview delegate item, and I observe a cpu usage very high when scrolling my list with lot of items, penalyzing the sm

Re: [Interest] QML and OpenGL conflicts

Here is where we currently are: - Threading our OpenGL code would currently mean having a thread between our project and Qt-related code. - Wrapping OpenGL code in makeCurrent() is not done and is not planned by the team due to optimizations and refactoring that never has been necessary. I agree it

Re: [Interest] QML and OpenGL conflicts

On 04/06/2015 14:25, Marc Gilleron wrote: > I tried to set QSG_RENDER_LOOP to "threaded" but didn't noticed any > difference, our application still crashes. Then you need to isolate why it crashes and choose a method to fix it. Some options: * Put your custom rendering into another thread and i

Re: [Interest] QML WebEngine causes segfault when started through steam

Hi, I had this problem few hours back and solved it using https://bugreports.qt.io/browse/QTBUG-42083?focusedCommentId=260806&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-260806 See if it works for you :) On Fri, Jun 5, 2015 at 6:29 PM, Mathias Baumann wrote: >

[Interest] QML WebEngine causes segfault when started through steam

Hello, I am using the QML WebEngine in my application. It seems to work okay when I run it normally. In my VM it just shows a black window, so far so good, probably just a bug related to the VM, I don't worry too much about that. My System and the VM are both Windows 7, 64bit (however a 32 bit a

Re: [Interest] ListElement value cannot be a property script

Thank you. The workaround works. But now the question is for Qt developers: Is there any possibility that in the near future this will be solved without using these kind of workaround that can be a annoying with long and complex data ? Thanks, Gianluca. > On 5 Jun 2015, at 12:10, Kristoffersen

Re: [Interest] ListElement value cannot be a property script

Hello, The way I’ve been working around this limitation is to add the list elements programmatically in a Component.onCompleted: script. ListModel { id: example Component.onCompleted: { append(“name”: "Alexander" +

[Interest] ListElement value cannot be a property script

Hello, I have a ListElement as following: ListElement { name: "Alexander"+qsTr("Sales Executive, Russia")+"" And QML complain to load it because I cannot use script as property value for ListElement. But if I write the following: ListElement { name: qsTr("AlexanderSales Executi