Latest Contributions by JonathonGrivas

I'm trying to generate a somewhat large geodatabase, it has 7 layers but a few of them have image attachments and the whole thing comes out to several gigabytes. When I run this using the code in the qml sample for v100, it takes about 20 minutes and then says "File not found Error with download, geodatabase file is not present at the expected path.".   If I  remove some of the layers from the replica request, this does not happen.  Does anyone know what might be going wrong or how I can further test this?  Additionally, running the same task on Android results in the app just spontaneously closing with no message of any kind in Qt Creator or on the device. I'm assuming this is an out of memory exception as the task eventually uses 6GB of ram on my desktop.  Is there any way to get the task to run safely on mobile, or are we going to have to pre-generate geodatabases and download/register them to get around this?  Thanks, Jon ... View more

MapView.identifyLayer seems to work well, it fires off a single request and returns a Feature object which has all the feature's fields and attributes. That feature comes from an instance of FeatureTable that I never created directly and prior to this query had no reference to, so I'm a bit weary to trust it.  FeatureLayer.selectFeaturesWithQuery is used in the feature attribute update example.  This sent me down a very confusing path as I didn't realize that waiting for the feature to "load" after you've already waited for the feature response was necessary.  I now see this in the example, but I was originally working from the documentation which doesn't say anything about this. Feature is a loadable, but it's not mentioned that while the feature object and its properties/methods are usable before loading, that the feature's attributes aren't all available until after loading.  The peculiar part about this is that it results in having to wait for two chained requests in order to accomplish what a single request would have accomplished, thus making a non-loadable version actually faster. FeatureTable.queryFeatures seems to work the exact same as selectFeaturesWithQuery, only you obviously have to select the feature yourself if you want it selected.  I noticed that I can actually just use MapView.identifyLayer's result as my feature object, even though it comes from an unknown FeatureTable. This results in only a single request being fired off, but literally the exact same response as doing the triple-request chain that occurs in the example.  My questions: Where does MapView.identifyLayer get its FeatureTable instance? It's different than the one I created.  Can I update a feature in my own FeatureTable instance with the feature from MapView.identifyLayer? I've tried this and it seems to work for feature attributes, but I'm having difficulty with attachments. Is there a way to get a feature's full data in a single request AND be able to edit it? It seems unreasonable to require 3 or even 2 requests for the same data to accomplish this. I confirmed this can be seen in the feature attribute update example if you monitor http requests.  The initial click triggers two requests, and hitting update triggers another. All 3 requests query for the same feature.  ... View more

In my ArcGIS Runtime v100.0 QML app, I'm experiencing a seemingly UI-caused crash which I am attempting to debug.  When I run in debug mode, the app crashes with exceptions before ever reaching that UI crash.  I am having difficulty debugging it due to my inexperience both with C++ and with the Qt/ArcGIS Runtime SDK architecture.   The exception I receive is: Exception at 0x7ffca7841f28, code: 0xe06d7363: C++ exception, flags=0x1 (execution cannot be continued) (first chance) in runtimecore!kdu_tile::get_mct_dwt_info I am dynamically creating/deleting feature layers and tables with this function: function changeLayer(layerId){   if(featureLayer!==null){     if(featureTable!==null){       featureLayer.featureTable.destroy();     }     featureLayer.destroy();   }   var layerToRemove = null;   map.operationalLayers.forEach(function(layer,layerIndex){     if(layer === featureLayer){       layerToRemove = layerIndex;     }   });   if(layerToRemove !== null){     map.operationalLayers.remove(layerToRemove);     console.log("removed",layerToRemove);   }   featureLayer =  ArcGISRuntimeEnvironment.createObject("FeatureLayer",{},map);   featureLayer.selectFeaturesStatusChanged.connect(selectFeaturesStatusChanged);   var featureTableConfig = {     url: featureServerUrl+layerId,     featureRequestMode: Enums.FeatureRequestModeOnInteractionCache,     credential: userCred   };   featureTable = ArcGISRuntimeEnvironment.createObject       ("ServiceFeatureTable",featureTableConfig,featureLayer);   featureLayer.featureTable = featureTable;   featureLayer.featureTable.loadStatusChanged.connect(function(){     if(featureLayer.featureTable.loadStatus==Enums.LoadStatusLoaded){       actionBar.title = featureLayer.featureTable.tableName;       var tempArr =[];       for(var i=0,l=featureLayer.featureTable.fields.length;i<l;i++){         if(featureLayer.featureTable.fields[i].editable){           tempArr.push(featureLayer.featureTable.fields[i]);         }       }       featureFields = tempArr;     }   });   map.operationalLayers.append(featureLayer); } And this is the qml structure of the map on component load: MapView {   id:mapView   anchors.fill: parent   wrapAroundMode: Enums.WrapAroundModeDisabled   attributionTextVisible : false   Map {     id: map     // add the BasemapImagery basemap to the map     ArcGISTiledLayer {       url: baseMapUrl     }   }   onMouseClicked: {     mapView.identifyLayerWithMaxResults       (featureLayer, mouse.x, mouse.y, 22, false, 1000);   }     onIdentifyLayerStatusChanged: {     if (identifyLayerStatus === Enums.TaskStatusCompleted) {       if (identifyLayerResult.geoElements.length >0){         var geoElem = identifyLayerResult.geoElements[0];         params.objectIds = [geoElem.attributes.attributeValue("objectid")];         featureLayer.selectFeaturesWithQuery(params, Enums.SelectionModeNew);       }     }   }   QueryParameters {     id: params     maxFeatures: 1   }   } This is the part of the changeLayerId function where the crash seems to be occurring:  featureTable = ArcGISRuntimeEnvironment.createObject     ("ServiceFeatureTable",featureTableConfig,featureLayer); ... View more

Hello again, I'm still working in v100.0 and I've decided to test the feature table caching. The default mode (OnInteractionCache) seems to cache features that are already on screen, and the only time it doesn't send out a request is if I zoom in on a point that's already on screen.  If I pan back and forth within the same small area, it sends requests every time and it receives the exact same responses every time. I thought the cached features would persist in memory  even if you change extents and come back, is that wrong? ... View more