Latest Contributions by JenniferNery

You can create your own FlareClusterer and override OnCreateGraphic(). You can try the following code: public class MyFlareClusterer : FlareClusterer  {    protected override Graphic OnCreateGraphic(GraphicCollection cluster, ESRI.ArcGIS.Client.Geometry.MapPoint point, int maxClusterCount)   {    if (cluster != null)    {     if (cluster.Any(g => g.Selected))     {      var graphics = new GraphicCollection(cluster.Where(g => g.Selected));      return base.OnCreateGraphic(graphics, point, maxClusterCount);     }     else     {      foreach (var g in cluster)       return g;     }    }    return null;   }    } I'm not sure if you wanted to refresh the cluster when selection is changed, but if you are using Editor. You can trigger clustering by subscribing to EditCompleted event.     private void Editor_EditCompleted(object sender, Editor.EditEventArgs e)     {      if(e.Action == Editor.EditAction.Select)      {       var l = MyMap.Layers["CensusDemographics"] as FeatureLayer;       l.Clusterer.ClusterGraphicsAsync(l.Graphics, MyMap.Resolution);      }     } You can look at tweak this SDK sample: http://help.arcgis.com/en/webapi/silverlight/samples/start.htm#FeatureLayerSelection. Remove the ArcGISDynamicLayer, change FeatureLayer.Mode to OnDemand, remove the "Renderer="{StaticResource YellowMarkerRenderer}"" and add the following:     <esri:FeatureLayer.Clusterer>      <local:MyFlareClusterer FlareBackground="Yellow"                                 FlareForeground="#99000000"                                 MaximumFlareCount="20" Radius="10" Gradient="{StaticResource BlueGradient}" />     </esri:FeatureLayer.Clusterer> Under Resources, you can set your gradient. <LinearGradientBrush x:Key="BlueGradient" MappingMode="RelativeToBoundingBox" >     <GradientStop Color="#990011FF" Offset="0"/>     <GradientStop Color="#990055FF" Offset="0.25"/>     <GradientStop Color="#990099FF" Offset="0.5"/>     <GradientStop Color="#9900CCFF" Offset="0.75"/>     <GradientStop Color="#9900FFFF" Offset="1"/>    </LinearGradientBrush> ... View more

I see. If the selection is not based on geometry but rather through a query. I would still recommend FeatureLayer if you plan to use AttachmentEditor, FeatureDataForm, FeatureDataGrid because FeatureLayer keeps service metadata information (i.e. Fields, Domains, etc). It may be a good idea to make it OnDemand mode too if you're only concerned about displaying features within map's current extent. You can still update FeatureLayer.Where clause and call FeatureLayer.Update(), this will re-query the service. If you plan to use Snapshot mode, you may hit service limit but in this case if all features are on the client, you can use Linq query instead to filter the features on the layer. This may help you decide which mode to use: http://help.arcgis.com/en/webapi/silverlight/help/index.html#/Feature_layers/016600000015000000/ ... View more

Have you looked at this SDK sample? http://help.arcgis.com/en/webapi/silverlight/samples/start.htm#SelectGraphics or this? http://help.arcgis.com/en/webapi/silverlight/samples/start.htm#CustomSymbols. You can highlight the graphic by providing VisualStates (MouseOver). ... View more

Sorry for the confusion. I meant v3.0 Pre-Release already have the fix. As for your concern about moving to Silverlight 5, we are currently considering making v3.0 available for Silverlight 4 as well. ... View more

Yes, you are correct. Mixed geometry types are not supported. You can quickly check this by running Fiddler. When it makes a request to GeometryService, you can check "geometries" property if its mixed or if separate requests are made per type. ... View more