Latest Contributions by LucasDanzinger

‎02-03-2021

Hello, Can you please provide some details on which swipe tool you are using in the MapView? That will help me better understand what you are looking for in 3D. Thanks, Lucas

‎01-25-2021

I took this code an ran it successfully on my machine - the map loads and displays. Do you have network connection? What platform are you testing on?

‎01-20-2021

Can you connect to the loadStatusChanged and get the error.message and error.additionalMessage when it fails? What does it say? onLoadStatusChanged: { if (loadStatus === Enums.LoadStatusFailedToLoad) { console.log("Error:", error.message, error.additionalMessage); } }

‎01-19-2021

We hit a similar issue, but I was able to reproduce the problem standalone. So either what you are seeing is a red herring or we are hitting different issues. In my case, the WebEngineProcess wasn't getting copied from the Qt Kit to my app bundle: To workaround, I went into my Qt Kit and grabbed "QtWebEngineProcess.app" and copied it to: AppName.app\Contents\Frameworks\QtWebEngineCore.framework\Helpers\QtWebEngineProcess.app This seems to be the Qt issue I was hitting - https://bugreports.qt.io/browse/QTBUG-86759

‎01-13-2021

This is due to a change in Qt starting at 5.15. The solution is to either stick with Qt 5.15 and upgrade to Runtime 100.9, or if you need to stick with Runtime 100.8, downgrade Qt versions to 5.12/13/14. Details on this change are highlighted in this blog - https://community.esri.com/t5/arcgis-runtime-sdks-blog/qml-api-breaking-changes-with-5-15/ba-p/888652

‎01-11-2021

From your psuedocode, it looks like whenever draw is called, you will create and add a new overlay. Is it possible to just add a single new graphic to your overlay instead of adding a completely new overlay each time? An overlay can contain any number of graphics, so in general, it would be advised to add graphics to an existing overlay rather than having a separate overlay for each individual graphic.

‎01-11-2021

The QML callout draws a shape using a Canvas and then displays it on the screen using the LocationToScreen API. Whenever the MapView's viewpoint changes, the draw location is updated with a new screen point. I think you could use the same workflow for your widgets based app. Here is an example workflow: - Get the Point location of your feature - Call locationToScreen and pass in your features geometry - https://developers.arcgis.com/qt/latest/cpp/api-reference/esri-arcgisruntime-mapview.html - Display your graphic at that location - Whenever the MapView's viewpoint changes (user pans/zooms), re execute this routine

‎12-29-2020

Thanks for reporting this. We've identified where this is going wrong. The crux of the problem is with the initialization order, where TileInfo assumes origin point is valid before it is. Here is some workaround code that works (although it is pretty ugly...) import QtQuick 2.6 import QtQuick.Controls 2.2 import Esri.ArcGISRuntime 100.9 as Esri ApplicationWindow { id: appWindow width: 800 height: 600 title: "ImageTiledLayer bug" function createOrigin() { return Esri.ArcGISRuntimeEnvironment.createObject("Point", { x: -20037508.34, y: +20037508.34, spatialReference: webMercator }); } Esri.SpatialReference { id: webMercator wkid: 3857 } function createLods() { let lods = []; lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 0, resolution: 156543.03390624999884, scale: 591657527.50934994221})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 1, resolution: 78271.516953124999418, scale: 295828763.7546749711} )); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 2, resolution: 39135.758476562499709, scale: 147914381.87733748555})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 3, resolution: 19567.879238281249854, scale: 73957190.938668742776})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 4, resolution: 9783.9396191406249272, scale: 36978595.469334371388})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 5, resolution: 4891.9698095703124636, scale: 18489297.734667185694})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 6, resolution: 2445.9849047851562318, scale: 9244648.867333592847} )); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 7, resolution: 1222.9924523925781159, scale: 4622324.4336667964235})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 8, resolution: 611.49622619628905795, scale: 2311162.2168333982117})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 9, resolution: 305.74811309814452898, scale: 1155581.1084166991059})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 10, resolution: 152.87405654907226449, scale: 577790.55420834955294})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 11, resolution: 76.437028274536132244, scale: 288895.27710417477647})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 12, resolution: 38.218514137268066122, scale: 144447.63855208738823})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 13, resolution: 19.109257068634033061, scale: 72223.819276043694117})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 14, resolution: 9.5546285343170165305, scale: 36111.909638021847059})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 15, resolution: 4.7773142671585082653, scale: 18055.954819010923529})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 16, resolution: 2.3886571335792541326, scale: 9027.9774095054617646})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 17, resolution: 1.1943285667896270663, scale: 4513.9887047527308823})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 18, resolution: 0.59716428339481353316, scale: 2256.9943523763654412})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 19, resolution: 0.29858214169740676658, scale: 1128.4971761881827206})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 20, resolution: 0.14929107084870338329, scale: 564.24858809409136029})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 21, resolution: 0.074645535424351691645, scale: 282.12429404704568014})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 22, resolution: 0.037322767712175845822, scale: 141.06214702352284007})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 23, resolution: 0.018661383856087922911, scale: 70.531073511761420036})); lods.push(Esri.ArcGISRuntimeEnvironment.createObject("LevelOfDetail", {level: 24, resolution: 0.0093306919280439614556, scale: 35.265536755880710018})); return lods; } function createTileInfo() { return Esri.ArcGISRuntimeEnvironment.createObject("TileInfo", { origin: createOrigin(), dpi: 96, tileWidth: 256, tileHeight: 256, spatialReference: webMercator, levelsOfDetail: createLods() }); } Esri.MapView { anchors.fill: parent focus: true Esri.Map { Esri.ImageTiledLayer { fullExtent: Esri.Envelope { xMin: -20037508.34; yMin: -20037508.34; xMax: +20037508.34; yMax: +20037508.34; spatialReference: Esri.SpatialReference { wkid: 3857 } } noDataTileBehavior: Esri.Enums.NoDataTileBehaviorBlank tileInfo: createTileInfo() tileCallback: function(level, row, column) { return "" } } } } }

‎12-10-2020

Hey Jeremy, 100.7 officially supports Catalina and Mojave - https://developers.arcgis.com/qt/latest/qml/guide/system-requirements-100-7.htm#ESRI_SECTION1_BDCD141D98EE4210B2F5ABF3BFE37185 We are in the process of finishing our 100.10 release, which will be our first release to officially support Big Sur. Our general cadence is that we try to support the latest 2 releases of macOS with each new release. We don't go back and re-certify older releases on newer operating systems. Is it possible to coordinate the upgrade with the 100.10 release in January? Otherwise, if you must upgrade now, it might be worth trying to upgrade a single test machine first to do some testing to see if you encounter any issues before pushing it out to everyone.

‎12-08-2020

You can use Viewpoints to programmatically move around the MapView. There are many different ways to go about it, several of which are showcased in this sample - https://github.com/Esri/arcgis-runtime-samples-qt/tree/master/ArcGISRuntimeSDKQt_CppSamples/Maps/ChangeViewpoint

‎12-08-2020

For the symbol, you have a few options. The simplest would be to create an image of what you want and use PictureMarkerSymbol. The main downside with that is that it won't scale well if you need to increase size of the image. This sample is in 2D but the same workflow will work in 3D - https://github.com/Esri/arcgis-runtime-samples-qt/tree/master/ArcGISRuntimeSDKQt_CppSamples/DisplayInformation/Picture_Marker_Symbol The next solution would be to design the symbol that you want in ArcGIS Pro and share it via a stylx file. This will give you the most customization. Here is a sample that shows how to consume a style file - https://github.com/Esri/arcgis-runtime-samples-qt/tree/master/ArcGISRuntimeSDKQt_CppSamples/DisplayInformation/ReadSymbolsFromMobileStyle Finally, you could create a multilayer symbol in code. For example, one symbol layer could be the circle and the other symbol layer could be an arrow. For example, VectorMarkerSymbolLayer allows you to define the vector shape of the symbol, similar to an SVG - https://developers.arcgis.com/qt/latest/cpp/api-reference/esri-arcgisruntime-vectormarkersymbollayer.html Once you have your symbol, you can update the heading to match the direction of the track using Renderer Scene Properties. Here is a sample showing this https://github.com/Esri/arcgis-runtime-samples-qt/tree/8252c8205325f0b5ce9c1e3145d3ba8c6da744d3/ArcGISRuntimeSDKQt_QMLSamples/Scenes/ScenePropertiesExpressions

‎11-30-2020

From what I understand of your workflow, the ArcGIS Runtime recommended pattern would be to use Feature attachments and Feature Services - these support adding image files alongside a database record, but they require you to publish a feature service in ArcGIS Online or ArcGIS Enterprise. Here is a sample that demonstrates this - https://github.com/Esri/arcgis-runtime-samples-qt/tree/master/ArcGISRuntimeSDKQt_QMLSamples/EditData/EditFeatureAttachments. Is this an option for you? If not, it might be worth posting the question on the Qt forums - https://forum.qt.io/

‎11-25-2020

Hi Norbert - Due to many very large architectural changes in Qt 6, we won't have a release of Runtime SDK that will work with Qt 6 when it is first released. Changes to the rendering stack will be the biggest change, but there are also changes to the asynchronous workflows and QML environment that will take some time to adapt to. As such, the Runtime SDK will be based on 5.15.x for at least the next several releases. We are still in the early stages of planning out all of the impacts and changes related to a Qt 6 upgrade (some of the pattern changes will likely require breaking API changes). At the moment, we are not sure of a timeline for which we will have a Qt 6-based SDK available. Can you share with me your plans, requirements, and timeline so we can take this into account? Thanks, Lucas

‎11-25-2020

As Big Sur was just released a few weeks ago, our previous releases have not been tested and do not list Big Sur as a supported platform. Historically, most upgrades "just worked" regardless of an official support statement from us, so it is unclear at this point if Big Sur is any different or not. Here is the 100.6 system requirements - https://developers.arcgis.com/qt/latest/qml/guide/system-requirements-100-6.htm -- High Sierra and Mojave are the 2 supported versions of macOS. We are currently working on finishing up our 100.10 release, and we intend to fully test and support Big Sur for that release.

‎11-25-2020

Do you have any more details on the workflow? Are you using AppStudio?

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by LucasDanzinger

Re: Swipe Tool for 3D Mesh Models

Re: retryLoad is no work

Re: retryLoad is no work

Re: WebView not working after running macdeployqt.

Re: Cannot Move createObject

Re: GraphicOverlay on MapView blinking, how to fix?

Re: Responsive label displaying symbol name and coordinates and block zoom due to mouse events on map

Re: ImageTiledLayer in QML crashes on 100.8 and 100.9

Re: Is 100.7 supported on Mac OS Big Sur?

Re: Pan and zoom pushbuttons on map in arcgis 100.6 qt cpp

Re: How to draw a combined Graphics consisting of a circle and a direction line?

Re: post image to website servr using javascript

Re: ArcGIS RuntimeQt and Qt6?

Re: Segmentation fault since macOS 11 Update

Re: post image to website servr using javascript

Re: Possible memory leak with Dictionary Renderer ...

Logging into the future: Introducing the Next Gene...

Re: Ubuntu 24.04 Qt Version 6.4.2 is not compatibl...

Re: Windows Deployment

Re: Converting image into .tpk format