Latest Contributions by DominiqueBroux

If this error seems random, it might be a temporarly network issue or a server time out. To avoid the exception, you can wire up an Handler to the event Layer.InitializationFailed and log or display the error in the handler. ... View more

Depending on the type of legend item you want to customize, you can redefine the LegendItemTemplate and/or the LayerTemplate and/or the MapLayerTemplate. For example to redefine the lower level of legend item (the level with a swatch and a label) you can redefine the LegendItemTemplate with XAML code like: <esri:Legend Map=.........>   <esri:Legend.LegendItemTemplate>     <DataTemplate>       <StackPanel Orientation="Horizontal">         <Image Source="{Binding ImageSource}" HorizontalAlignment="Center" VerticalAlignment="Center"           Stretch="None" MinWidth="20" />         <TextBlock Text="{Binding Label}" Margin="5,0,0,0" VerticalAlignment="Center" />       </StackPanel>    </DataTemplate>   </esri:Legend.LegendItemTemplate> </esri:Legend> ... View more

I might miss something but what is not working if you:    create a ChildWindow call Show on this ChildWindow call SaveEdits close the child window in the SaveEditsFailed or EndSaveEdits handler ? ... View more

You can also calculate the mid point at client side, see this LinearReferencing sample using the Silverlight/WPF API (midpoint is a particular case that you can get by: var midPoint = line.LinearPosition(line.Length()/2); ) ... View more

The NormalizeCentralMeridian method transforms a geometry to stay within the -180/+180 extent. In case of a polyline or polygon crossing the dateline, the result is a polyline with 2 paths (and respectively a polygon with 2 rings), one close to -180 and the other close to +180 longitude. You can look at the ShowMapExtent sample which uses the method NormalizeCentralMeridian. Most generally you don't need to normalize a geometry for working at client side. More useful for the storage at server side. ... View more

You can call the Initialize method by code. Once the feature layer is initialized, the Initialized event will be fired and the metadat will be available. ... View more

You pointed out a design issue that should not impact the runtime. However, when the same legend control is incorperated/merged into an app based on either the standard or the showcase template, that legend gets stuck. I am talking about 3.0 API here. How could one explain that it works with one ESRI thing and doesn't with another ESRI thing? I don't figure out any reason for that. Could you share more détails on how to reproduce this issue? Thanks ... View more

To cross the meridian, you need either to use X coordinates < -180 or > 180, or you need to create 2 rings for your geometry. In your case: NE point: Lat 45, Lon 182 (east of the meridian) SE point: Lat 40, Lon 182 SW point: Lat 40, Lon 176 (west of the meridian)j NW point: Lat 45, Lon 176 NE point: Lat 45, Lon 182 (to join to the original point and complete the polygon) Then you can normalize that geometry and you'll get 2 rings. ... View more

You have to set the attached property esri:GraphicsLayer.MapTipAutoPosition="True" to the maptip. There is a sample here: http://resources.arcgis.com/en/help/silverlight-api/samples/start.htm#BatchGeocoding ... View more

but it is the "legend or Layer List" that become uncontrollable or un-expandable. .... The essential functionality for layer listing and legends for "composite" map services fails in the Silverlight API due to this error, That's not normal. The issue you pointed out is a design time issue that doesn't impact the runtime. Could you give more infos on how to reproduce your issue? I believe ESRI might already have a work-around for this, To avoid this runtime issue you can either initialize the Legend.LayerIds by code instead of XAML, or you can also keep it uninitialized and set ShowLegend to false on the layers you don't want to see in the legend. ... View more

That's a message that appears only in design time Inside Visual Studio. However you should be able to compile and run your application despite this message. ... View more

I am not able to reproduce this issue. Could you share a repro case? The app does a lot of custom Dispose work to get memory at a minimum as users are constantly opening and closing new maps in the same application instance Sidenote: ArcGIS Silverlight API is already releasing the memory as soon as it's no more useful. So I am not sure you gain that much by doing it yourself (though I am not aware of your context, so...) ... View more

My best bet is that your map doesn't contain FeatureLayer only, so in your loop, myFeatureLayer can be null. ... View more