POST
|
I've tested this out with version 100.5 and it appears to be fixed. Thanks!
... View more
04-17-2019
03:07 PM
|
2
|
0
|
3485
|
POST
|
Hello, I am using version 100.4 of the runtime. It seems that the SketchEditor's default double-click to finish behavior is different between Android and the other platforms. When sketching a line or polygon on Windows or iOS, the point that is double-clicked to finish the sketch will be part of the final geometry. However, on Android the point that is double-clicked will not be part of the geometry, only the points that we're added already. Here is how I am using the SketchEditor: await mapView.SketchEditor.StartAsync(SketchCreationMode.Polyline, false); Cheers, Jeff
... View more
03-18-2019
11:58 AM
|
0
|
1
|
601
|
POST
|
Hello, I am using version 100.4 of the ArcGIS .NET runtime. I have noticed that attachments with names longer than 40 characters (not including the file extension) will always have a size of zero when returned from ArcGISFeature.GetAttachmentAsync(). Note: An attachment name longer than 40 characters appears to be truncated to 40 characters. Here is an example: // Name is truncated to "Google Play Distribution Agreement (SP C.pdf"
await myFeature.AddAttachmentAsync("Google Play Distribution Agreement (SP Comments).pdf", "application/pdf", <attachmentData>);
await myFeature.FeatureTable.UpdateFeatureAsync(myFeature);
if (myFeature.FeatureTable is ServiceFeatureTable serviceFeatureTable)
{
var editResults = await serviceFeatureTable.ApplyEditsAsync();
var featureResult = (FeatureEditResult)editResults.FirstOrDefault();
var attachmentResult = featureResult.AttachmentResults.First();
var id = attachmentResult.ObjectId;
var allAttachments = await myFeature.GetAttachmentsAsync();
// This will have a size of 0
var myAttachment = allAttachments.FirstOrDefault(a => a.Id == id);
}
If you rename the same file to have name shorter than 40 characters, the size will be set correctly. I have attached the offending file. This only occurs after the attachment was added to the feature. If the attachment already exists on myFeature then GetAttachmentsAsync() returns the attachments with correct sizes. The attachment returned from AddAttachmentAsync() has the correct size, but of course does not have the correct id yet. I managed to work around this by doing something like this: var data = await attachment.GetDataAsync();
var size = data.Length; Cheers, Jeff
... View more
01-23-2019
11:40 AM
|
0
|
2
|
648
|
POST
|
Hello, I am using version 100.4 of the runtime. I have an AGOL hosted feature layer that is set to track the creator and editors of a feature: However, I cannot get these settings be respected when creating or editing features in a GeodatabaseFeatureTable. The fields are always empty. I was able to get this working with ServiceFeatureTables by setting the Credential property before adding or updating a feature, causing a token to be sent with the add/update request. I have tried the following: - Setting the Credential property on the OfflineMapSyncJob object that is returned from OfflineMapSyncTask.SyncOfflineMap. This throws an exception with a message saying to use the AuthenticationManager. - Before syncing: Adding a Credential to the AuthenticationManager that matches the Geodatabase.Source property. I can see in fiddler that this causes a token to be sent with the request to FeatureServer/uploads/upload, but the creator/editor fields are still not set. - Before creating the feature: Adding a Credential to the AuthenticationManager that matches the Geodatabase.Source property. Inspecting the feature that is returned from GeodatabaseFeatureTable.CreateFeature() shows that the creator/editor fields are empty. Is it possible to set "Creator" and "Editor" fields when working with features in a GeodatabaseFeatureTable?
... View more
01-04-2019
03:04 PM
|
0
|
1
|
464
|
POST
|
Hello, I am using version 100.4 of the .NET runtime. I have noticed in several different applications that the magnifier does not work correctly when using the SketchEditor. The issue is that the magnifier will always result in a new point being sketched in the top left corner of the visible map area, and not where the crosshairs are located. Steps to Reproduce. 1). Start the SketchEditor in any editing mode. 2). Long press on the map to show the magnifier 3). Move the magnifier from its initial location 4). Remove your finger Notice that a point was not sketched at the last location of the magnifier crosshairs, but instead in the top left corner of the visible map area. I am wondering if there is there a way to workaround this? EDIT: I tested the magnifier in the same application with version 100.3 of the runtime and it worked, so it would seem this issue was introduced in version 100.4 Thanks, Jeff
... View more
11-27-2018
10:01 AM
|
0
|
3
|
4015
|
Title | Kudos | Posted |
---|---|---|
2 | 04-17-2019 03:07 PM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:25 AM
|