POST
|
Xiuju, Thank you for your report. We are aware of this issue and currently looking into it. The fix will be available soon. In the meantime you can use "CommitButton" as the name for your "SaveButton" button in your custom template to workaround the issue. We apologize for the inconvenience.
... View more
05-09-2011
01:49 PM
|
0
|
0
|
125
|
POST
|
Markus, Yes, you are right. FeatureDataGrid's ItemsSource does not implement ICollectionView in v2.1 and unfortunately, that becomes a known limit for the version you are using 😞 However; you can use the 2.2 Beta version of the API from here to overcome this issue. Sorry for the inconvenience!
... View more
05-05-2011
08:43 AM
|
0
|
0
|
323
|
POST
|
Markus, FeatureDataGrid uses PagedCollectionView as its ItemsSource. Any operation such as sorting that relies on cultural information needs to be indicated for PagedCollectionView. You can use the following code snippet to achieve your sorting use case and please make sure that the GraphicsLayer property of your FeatureDataGrid is set before doing this:
System.Windows.Data.PagedCollectionView itemsSource = MyDataGrid.ItemsSource as System.Windows.Data.PagedCollectionView;
itemsSource.Culture = System.Threading.Thread.CurrentThread.CurrentCulture;
Hope this helps.
... View more
05-04-2011
10:56 AM
|
0
|
0
|
323
|
POST
|
Joel, Thank you for your post. We are currently looking into this problem and the fix will be available soon. In the meantime you can use the following code snippet when you are setting the AttachmentEditor's GraphicSource property:
Dispatcher.BeginInvoke((Action)delegate()
{
yourAttachmentEditor.GraphicSource = yourGraphic;
});
Hope this helps.
... View more
04-18-2011
10:16 AM
|
0
|
0
|
133
|
POST
|
Haven't you set FeatureDataGrid's "Map" property? If you did, then you wouldn't need to perform the selection on your layer as FeatureDataGrid automatically selects the corresponding Graphic of the selected row on your map.
... View more
03-07-2011
07:59 AM
|
0
|
0
|
494
|
POST
|
3. Get reference to the predefined graphics layer and add the result graphic object to it. 4. Set GraphicsLayer and Map property of the FDG. Like mentioned in my previous post: In addition, if you're adding features to a GraphicsLayer and using this layer as the source of your FeatureDataGrid then date fields format won't match the format in SDE because these layers do not have field/attribute information as opposed to feature layers. Feature layers contain the LayerInfo.Fields object that the FeatureDataGrid control uses to populate its ItemsSource, i.e. some custom converters have been used for date fields, coded value domain fields, etc... Unfortunately, graphics layers do not have any information in regards to this and you have to write your own converters for your attributes.
... View more
02-22-2011
05:52 AM
|
0
|
0
|
644
|
POST
|
FeatureDataGrid DataContext property does not have any data in regards to the attributes table. You need to extract the attributes from the graphic collection of your FeatureLayer or the ItemsSource in FeatureDataGrid like mentioned in post #2. Hope this helps.
... View more
02-17-2011
01:39 PM
|
0
|
0
|
494
|
POST
|
FeatureLayer does not DataContext property as it is not of type FrameworkElement. Unfortunately, there is no such attribute table that you are looking for in feature layers and you would need to either iterate through the Graphic objects in your layer or FeatureDataGrid's ItemsSource in order to retrieve items attributes.
... View more
02-17-2011
10:13 AM
|
0
|
0
|
494
|
POST
|
Since you are dealing with multiple feature layers, I would advise that you set default values at the SDE level, i.e. for the required CodedValueDomain attributes associate a default value, say empty string as Code. Fields at the level of feature services are always considered as nullable data types and if you need to force them to be required an alternative approach would be extending current FeatureDataForm control and specifically look into the following method:
private bool HasChange(Control control, object valueInGraphic, Type type, out bool hasError)
{
}
... View more
02-17-2011
09:40 AM
|
0
|
0
|
260
|
POST
|
Sanjay, How are you populating the items in your FeatureDataGrid in these scenarios? The reason I'm asking this is that both the IdentifyTask and QueryTask objects return FeatureSet as their completed event handler arguments and none of them have any information about the field/attribute collection that could be retreived from the service itself (i.e. data types, etc...). FeatureDataGrid gets this field information from its associated layer (GraphicsLayer property) and uses appropriate converters and editing cell templates correspondingly. This is the reason that we always suggest developers NOT to set FeatureDataGrid's ItemsSource property directly as it will be populated by the control automatically with regards to its GraphicsLayer property. In addition, if you're adding features to a GraphicsLayer and using this layer as the source of your FeatureDataGrid then date fields format won't match the format in SDE because these layers do not have field/attribute information as opposed to feature layers. It would be also good if you could share some code snippets or explain more how you are showing the results in FeatureDataGrid if the above comments have not addressed your concerns.
... View more
02-17-2011
09:07 AM
|
0
|
0
|
644
|
POST
|
Jay, I suggest you to use the LIKE operator while querying string values. The following code snippet looks for all rows that contain the trimmed string in your FindAddress TextBox control:
query.Where = string.Format("Address LIKE '%{0}%'", FindAddress.Text.Trim());
... View more
02-10-2011
09:27 AM
|
0
|
0
|
477
|
POST
|
Correct! And I'm glad that you figured it out already 🙂
... View more
02-07-2011
07:54 AM
|
0
|
0
|
255
|
POST
|
Try this:
<Image x:Name="MyImage" Source="{Binding ImageField, StringFormat='/Assets/images/{0}'}" />
... View more
02-07-2011
06:50 AM
|
0
|
0
|
255
|
POST
|
This is a known issue in 2.1 and has been fixed for the 2.2 version of the API. For now please add a reference to System.Windows.Controls.Data.Input DLL in your project prior to drag-dropping any of the Toolkit controls in your Visual Studio design view.
... View more
02-04-2011
01:18 PM
|
0
|
0
|
216
|
POST
|
I think the easiest way would be having the same MouseLeftButtonUp event handler for all your feature layers and setting FeatureDataForm's FeatureLayer and GraphicSource properties based upon the values of the sender object and the GraphicMouseButtonEventArgs argument in your handler, i.e. in your XAML:
<esri2:FeatureDataForm x:Name="MyFeatureDataForm" ........... />
And in your code-behind:
private void FeatureLayer_MouseLeftButtonUp(object sender, GraphicMouseButtonEventArgs args)
{
FeatureLayer featureLayer = sender as FeatureLayer;
for (int i = 0; i < featureLayer.SelectionCount; i++)
featureLayer.SelectedGraphics.ToList().UnSelect();
args.Graphic.Select();
MyFeatureDataForm.FeatureLayer = featureLayer;
MyFeatureDataForm.GraphicSource = args.Graphic;
FeatureDataFormBorder.Visibility = Visibility.Visible;
MyPopup.IsOpen=true;
}
... View more
02-04-2011
12:43 PM
|
0
|
0
|
168
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|