Re: [Interest] Build fail and OpenGL
Indeed, that line is not found in GLES2/gl2.h. The source comes from Toradex_CE800 SDK, which they provide in support of their Colibri VF61 SOM and eval board. I'll take the issue up with them. Thanks for the help! Mike -Original Message- From: Interest [mailto:interest-bounces+mnelson=sutron@qt-project.org] On Behalf Of Thiago Macieira Sent: Friday, July 15, 2016 12:09 PM To: interest@qt-project.org Subject: Re: [Interest] Build fail and OpenGL On sexta-feira, 15 de julho de 2016 08:25:03 PDT Michael R Nelson wrote: > c:\qt\5.6\src\qtbase\include\qtgui\../../src/gui/opengl/qopengles2ext. > h(22) > : error C2146: syntax error : missing ';' before identifier 'GLint64' > > Can someone help me understand why the build fails? Is it because I've > not properly addressed lack of hardware acceleration somehow? Is there > a configure option I need to specify to address this point? That line is: typedef khronos_int64_t GLint64; Looks like your GLES/gl2.h header missed the definition of khronos_int64_t. Can you confirm that your OpenGL headers are broken? Can you find out what source of OpenGL headers you have? Do they come with Windows? With a driver? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Managing memory with QObject*-models exposed to QML
Hi, In my humble opinion, QObjectListModel is a bad idea. Because it is difficult to manage the life cycle of QObject with QML. Just like your problem. I have met the similar issue in my first QML project. The application always crashes. The pattern is purely random. I wasted a lot of time to discover the root cause. Moreover, I am doubt to use a list of QObject as a data storage class. Since QObject is not copyable, it must use a pointer to share QObject to multiple classes. Extra care is needed to manage its life cycle. And they are not able to be passed to another thread for processing directly. Therefore, I always prefer an implicitly shared class over a list of QObject as data storage. It is copyable and thread safe (using a worker model). Instead, I use another approach for sharing data between C++ and QML. I just hold a QList (T is an implicitly shared class) as the central data storage in memory. Whatever it is changed, it will update a QVariabtListModel to inform QML to render the content. However, QML/JS do not write to the model directly. Instead, it will ask another C++ object to update the central data. (e.g by context object / messaging system) In order to simplify the process to update the QVariantListModel, I have written a library called QSyncable. It have document and example code to demonstrate how this approach works. https://github.com/benlau/qsyncable On 14 July 2016 at 17:02, Ola Røer Thorsenwrote: > I've found that creating C++ models containing a list of QObject* based on > QAbstractListModels and using them in Quick views such as ListView is very > useful. I'm not the only one, there are several implementations of > "QObjectListModel" around, and I've got my own as well. > > On quite rare ocations I have had crashes deep inside the QML engine > itself, that are very hard to reproduce, when rapidly adding and removing + > deleting objects in the model from C++. I think this probably has to do > with the Quick view's delegate that might still be using an Object that was > just deleted. > > I've made sure that all objects put into the list model are created in C++ > and they do have a parent to avoid qml taking ownership of them. When > removing from a model, they are first removed (beginRemoveRows, remove > from array, endRemoveRows), then finally deleted using > object->deleteLater(). > > My worry here is that deleteLater() is sometimes still too soon for the > QML engine to keep up, especially when there is a lot of things going on in > the Quick scene. > > Could this be the case? If so, what is the rock-solid way to do this? > > One ugly "fix" that I would like to avoid is to put the objects in some > queue and delete them after a given "safe time duration", like > "deleteMuchLater()". > > Another way idea that I have not tried is to use QSharedPointer, and > expose some wrapper Q_GADGET-based type to QML that contains this pointer > with some raw pointer property, but this introduces shared pointers to my > C++ application and changes a lot of other things. > > I'd appreciate any input on if this is a real problem to begin with, and > if so, how to work around it. > > Thanks, > Ola > > > > > > > ___ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > > ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Be aware: QtLocation's free MapQuest service discontinued
Hello, Also worth noting is that Esri will soon be pushing in an additional QtLocation provider plugin into the next minor and patch releases of the Qt framework. It will give you access to many of the Esri maps provided from ArcGIS online services. Also world geocoding and routing services will be available through the plugin. If you have any questions about Esri as a backend QtLocation provider, please don't hesitate to contact me. Thanks. -Michael Tims Lead Software Engineer ArcGIS Runtime SDK for Qt Esri http://developers.arcgis.com/qt On 7/14/16, 11:07 PM, "Interest on behalf of Alexander Blasche"wrote: >Hi, > >Qt Location provides three content/map provider plugins (HERE, MapBox and >MapQuest). The first two providers require an account to run and MapQuest >was free of any registration so far. Unfortunately this changed this >Monday. More details in: > >https://urldefense.proofpoint.com/v2/url?u=https-3A__bugreports.qt.io_brow >se_QTBUG-2D54599=CwICAg=n6-cguzQvX_tUIrZOS_4Og=KhEhoiXTE1wTwtxCJdnUb >w=yxQ8PiKLsdnKplLFUhgDgvQbOrirL_Dhpkp0OXGCHRA=G0dVHS4X3dX2c99T-VNCyhko >H8VvPNVsqCCydkzHAec= > >As a consequence any QtLocation application that uses MapQuest will no >longer receive any map tiles. The only possible way to fix this today is >to change from MapQuest to HERE or MapBox. Although those providers >require a registration they do offer free of charge usage models. Please >be aware of their terms and conditions though. > >We are very sorry for this problem but at the end of the day there is not >much Qt can do. We are working on a patch to change to a new registration >free provider and even a related indirection but at the end of the day, >registration free access is becoming a thing of the past. > >Going forward I would suggest to to always consider some form of >registered usage for any map provider. While we will continue to address >upcoming service changes this does ensure that there is some form of >business relationship between you and your chosen map tile provider. At >the very least it means that notifications can be received before >drastic changes happen. > >-- >Alex >___ >Interest mailing list >Interest@qt-project.org >https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.qt-2Dproject.org >_mailman_listinfo_interest=CwICAg=n6-cguzQvX_tUIrZOS_4Og=KhEhoiXTE1w >TwtxCJdnUbw=yxQ8PiKLsdnKplLFUhgDgvQbOrirL_Dhpkp0OXGCHRA=F2oKkurzAoHRrM >cqGU3xpgfGo9g54Wdk7drgTfU0QMA= ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Build fail and OpenGL
On sexta-feira, 15 de julho de 2016 08:25:03 PDT Michael R Nelson wrote: > c:\qt\5.6\src\qtbase\include\qtgui\../../src/gui/opengl/qopengles2ext.h(22) > : error C2146: syntax error : missing ';' before identifier 'GLint64' > > Can someone help me understand why the build fails? Is it because I've not > properly addressed lack of hardware acceleration somehow? Is there a > configure option I need to specify to address this point? That line is: typedef khronos_int64_t GLint64; Looks like your GLES/gl2.h header missed the definition of khronos_int64_t. Can you confirm that your OpenGL headers are broken? Can you find out what source of OpenGL headers you have? Do they come with Windows? With a driver? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Qt Location with Mapbox plugin?
Hi Do you see http://doc.qt.io/qt-5/location-plugin-mapbox.html and https://www.mapbox.com/help/define-map-id/ ? Cheers Guillaume - Mail original - > De: "Ola Røer Thorsen"> À: "interest" > Envoyé: Vendredi 15 Juillet 2016 13:43:25 > Objet: [Interest] Qt Location with Mapbox plugin? > I'm struggling getting any maps shown using the Qt Location Mapbox > plugin. I'm getting error messages like "failed to fetch tile, , > server replied: Forbidden". > The plugin needs a map_id and an access_token. > On the mapbox website it's easy to find the access tokens, but no map > id's. Maybe they have changed the way this is done? They refer a lot > to Style URLs instead. > Are any of you out there successfully using Mapbox? How did you > configure the plugin? > Cheers, > Ola > ___ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Qt Location with Mapbox plugin?
> Den 15. juli 2016 kl. 15:01 skrev "Olivier B." >: > > There was a message about it in that same mailing list earlier this morning > from alexander.blas...@qt.io : > Saw that but it's not relevant to my actual question. I am actually trying to use mapbox, not osm/mapquest that is now broken. > 2016-07-15 14:43 GMT+02:00 Ola Røer Thorsen : >> I'm struggling getting any maps shown using the Qt Location Mapbox plugin. >> I'm getting error messages like "failed to fetch tile, , server replied: >> Forbidden". >> >> The plugin needs a map_id and an access_token. >> >> On the mapbox website it's easy to find the access tokens, but no map id's. >> Maybe they have changed the way this is done? They refer a lot to Style URLs >> instead. >> >> Are any of you out there successfully using Mapbox? How did you configure >> the plugin? >> >> Cheers, >> Ola >> >> >> ___ >> Interest mailing list >> Interest@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/interest > > ___ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Qt Location with Mapbox plugin?
There was a message about it in that same mailing list earlier this morning from alexander.blas...@qt.io : Hi, Qt Location provides three content/map provider plugins (HERE, MapBox and MapQuest). The first two providers require an account to run and MapQuest was free of any registration so far. Unfortunately this changed this Monday. More details in: https://bugreports.qt.io/browse/QTBUG-54599 As a consequence any QtLocation application that uses MapQuest will no longer receive any map tiles. The only possible way to fix this today is to change from MapQuest to HERE or MapBox. Although those providers require a registration they do offer free of charge usage models. Please be aware of their terms and conditions though. We are very sorry for this problem but at the end of the day there is not much Qt can do. We are working on a patch to change to a new registration free provider and even a related indirection but at the end of the day, registration free access is becoming a thing of the past. Going forward I would suggest to to always consider some form of registered usage for any map provider. While we will continue to address upcoming service changes this does ensure that there is some form of business relationship between you and your chosen map tile provider. At the very least it means that notifications can be received before drastic changes happen. 2016-07-15 14:43 GMT+02:00 Ola Røer Thorsen: > I'm struggling getting any maps shown using the Qt Location Mapbox plugin. > I'm getting error messages like "failed to fetch tile, , server > replied: Forbidden". > > The plugin needs a map_id and an access_token. > > On the mapbox website it's easy to find the access tokens, but no map > id's. Maybe they have changed the way this is done? They refer a lot to > Style URLs instead. > > Are any of you out there successfully using Mapbox? How did you configure > the plugin? > > Cheers, > Ola > > > ___ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > > ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Building Qt/Android on Windows
After all I was able to build it. I set environment variables through Advanced System Settings (instead of command line) and add to Path variable. 2016-07-14 15:35 GMT+03:00 Oleg Evseev: > Hi, > > Trying to build Qt/Android 5.7 on Windows 7 SP1 x64 using this instruction > https://wiki.qt.io/Building_qt-android_on_windows > > Set environment variables: > > set "ANDROID_API_VERSION=android-23" > set "ANDROID_SDK_ROOT="d:\Android\sdk"" > set "ANDROID_TARGET_ARCH=armeabi-v7a" > set "ANDROID_BUILD_TOOLS_REVISION=23.0.3" > set "ANDROID_NDK_PATH="d:\Android\android-ndk-r10c"" > set "ANDROID_NDK_ROOT="d:\Android\android-ndk-r10c"" > set "ANDROID_TOOLCHAIN_VERSION=4.9" > set "ANDROID_NDK_HOST=windows" > > Run configure as in the instruction. > > When building got "Project ERROR: No suitable Android SDK platform found. > Minimum version is android-23." > > in qtbase ... && mingw32-make -f Makefile.distributedjar > > What am I missing? > > Thank you for help! > > --- > Regards, Oleg > ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Qt Location with Mapbox plugin?
I'm struggling getting any maps shown using the Qt Location Mapbox plugin. I'm getting error messages like "failed to fetch tile, , server replied: Forbidden". The plugin needs a map_id and an access_token. On the mapbox website it's easy to find the access tokens, but no map id's. Maybe they have changed the way this is done? They refer a lot to Style URLs instead. Are any of you out there successfully using Mapbox? How did you configure the plugin? Cheers, Ola ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Build fail and OpenGL
Hello, Trying to build Qt 5.6.1-2 for Colibri VF61, which has no hardware acceleration. configure -prefix c:\Qt\5.6\vf61 -platform win32-msvc2013 -xplatform wince80colibri-armv7-msvc2012 -nomake tests -nomake examples -commercial -confirm-license -release Build (nmake) fails on OpenGL: cl -c -FIqt_gui_pch.h -Yuqt_gui_pch.h -Fp.pch\release\Qt5Gui_pch.pch -nologo -Zm200 -Zc:wchar_t- -O2 -MT -EHs-c- -GR -W3 -w34100 -w34189 -DUND ER_CE -DWINCE -D_WINDOWS -D_UNICODE -DUNICODE -D_WIN32 -DQT_NO_PRINTER -DQT_NO_PRINTDIALOG -DQT_NO_CLIPBOARD -DQT_NO_ACCESSIBILITY -DQT_NO_NATIVE_GEST URES -DQT_NOSTANDARDSHELL_UI_MODEL -D_CRT_SECURE_NO_DEPRECATE -D_WIN32_WCE=0x800 -DARMV7 -D_AMRV7_ -Darmv7 -D_ARM_ -DUNDER_CE -DWINCE -DARM -DQT_NO_WI NCE_SHELLSDK -DQT_NO_WINCE_NUIOUSER -DQT_NO_USING_NAMESPACE -DPNG_ARM_NEON_OPT=0 -DQT_ENABLE_HARFBUZZ_NG -DENABLE_PIXMAN_DRAWHELPERS -DQT_BUILD_GUI_LI B -DQT_BUILDING_QT -D_CRT_SECURE_NO_WARNINGS -D_USE_MATH_DEFINES -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDE R -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x040800 -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_CORE_LIB -DQT_NO_EXCEPTIONS -DNDEBUG -IC:\Qt\5.6\S rc\qtbase\src\gui -I. -IC:\Qt\5.6\Src\qtbase\src\3rdparty\libpng -IC:\Qt\5.6\Src\qtbase\src\3rdparty\zlib -IC:\Qt\5.6\Src\qtbase\src\3rdparty\harfbuzz -ng\include -IC:\Qt\5.6\Src\qtbase\src\3rdparty\zlib -IC:\Qt\5.6\Src\qtbase\include -IC:\Qt\5.6\Src\qtbase\include\QtGui -I..\..\include -I..\..\inclu de\QtGui -IC:\Qt\5.6\Src\qtbase\include\QtGui\5.6.1 -IC:\Qt\5.6\Src\qtbase\include\QtGui\5.6.1\QtGui -Itmp -I/include -IC:\Qt\5.6\Src\qtbase\include\Q tCore\5.6.1 -IC:\Qt\5.6\Src\qtbase\include\QtCore\5.6.1\QtCore -IC:\Qt\5.6\Src\qtbase\include\QtCore -I..\..\include\QtCore -I.moc\release -IC:\Qt\5.6 \Src\qtbase\mkspecs\wince80colibri-armv7-msvc2012 -Fo.obj\release\ @C:\Users\MNELSO~1.WOR\AppData\Local\Temp\nmAE05.tmp qwindowsysteminterface.cpp c:\qt\5.6\src\qtbase\include\qtgui\../../src/gui/opengl/qopengles2ext.h(22) : error C2146: syntax error : missing ';' before identifier 'GLint64' Can someone help me understand why the build fails? Is it because I've not properly addressed lack of hardware acceleration somehow? Is there a configure option I need to specify to address this point? Thanks for any insight you can provide! Mike Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Be aware: QtLocation's free MapQuest service discontinued
Hi, Qt Location provides three content/map provider plugins (HERE, MapBox and MapQuest). The first two providers require an account to run and MapQuest was free of any registration so far. Unfortunately this changed this Monday. More details in: https://bugreports.qt.io/browse/QTBUG-54599 As a consequence any QtLocation application that uses MapQuest will no longer receive any map tiles. The only possible way to fix this today is to change from MapQuest to HERE or MapBox. Although those providers require a registration they do offer free of charge usage models. Please be aware of their terms and conditions though. We are very sorry for this problem but at the end of the day there is not much Qt can do. We are working on a patch to change to a new registration free provider and even a related indirection but at the end of the day, registration free access is becoming a thing of the past. Going forward I would suggest to to always consider some form of registered usage for any map provider. While we will continue to address upcoming service changes this does ensure that there is some form of business relationship between you and your chosen map tile provider. At the very least it means that notifications can be received before drastic changes happen. -- Alex ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest