...And then your whole initializer list might make sense.... Because as it is now, using float or double is going to make no difference anywhere. You're not understanding/specifying what that is an array of, and the compiler doesn't know, hence the message:
error: C2440: 'initializing': cannot convert from 'initializer list' to 'int'
To be specific, it's actually for your inner initializers. Compiler has told you it's expecting an array of ints. Instead it sees "an initializer list".
Well I've solved it in a stupid-but-working way, I had to install 5.10 on another computer anyway, so I took the maintenance tool from there and used it to delete the 5.10 with the buggy installation. Then reinstalled with the needed components.
The same issue with 3rd-party licenses also applies to users of the LGPL version.
I seems that most Qt users just ignore it. I had been asking a laywer what needs to be done and that resulted in a >40 pages document regarding Qt only.
Qt support just told that they don't have something else than the information on the website. The also told that the use of Qt does not need to be mentioned in case of a commercial license, but that this does not apply to the 3rd-party licenses within Qt.
Qt sales told that they would provide something when available, but nothing is currently available.
@davidino in addition to the good reply from @mrdebug, and although you're working with C++ (from your code snippet) you may want to take a look at this post, related to optimizing OpenCV and Python on the Raspberry Pi. Hopefully some hints may help you improve the performance of your environment.
Im trying to use a virtualmachine Linux now, but I have a similar problem. When trying to use QtCreator and make a Kit for my embedded board, there is an error saying I need a Qt version that is compatible with ARM, and I only have an x86 version.
What do I do to get a qmake that will compile for ARM?
Did you download already the complete source archive?
There is already a link given in my earlier post on bullet "Download Qt ..."
Basically you need to set up 2 environment variables and start configure. I believe there is a way to do through Qt creator,but so far I have found the way using configure easier. At the end of configure it tells you how to start the actual cross compilation.
After cross compilation you can bind the freshly cross-compiled Qt Libs with its qmake into Qt creator and use it from there.
It would also be nice if one of the "experts" in this forum answered this thread, as it seems pretty difficult to understand where Qt (5, at least) actually does pick up its default fonts from under various OSes....
Well, there's a very long story - and boring - to this; however, ultimately I came to create a complete separation of concerns. Qt didn't have anything in particular to offer that helped me (which is no slight against Qt) excepting some Xml parsing/manipulation code (which is very useful - but I already have code for that.)
Ultimately I couldn't use Qt or my previous SAML code (the majority of it) because the accepting Identity Service was using XmlSec to validate signatures in some fashion I could not discern (and they could not tell me) - so I had to use xmlsec myself to sign the assertions.
I'd still like to figure out why my assertion signing code worked with one IDP validator and did not work with this one - but I don't have time to do so right now.
Seems like it.... It come from the openPersistentEditor.... anyways, for now, I think I'll just change the default QStyleSheet at the creation of the Spinbox, and then change it back when the widget is accessed !... very weird !...
Great! I've published my CV. So feel free to contact me.
I have got an artistic and engineering experience. It seems it's exactly you are looking for.
I'm looking for full-time job (even short term). I don't like being too multi-tasked. I prefer take one task and finish it as soon as possible.