Latest Contributions by CharlesMacleod

So Max, I have looked closely at this and discussed with the original developer.This is designed behavior. Please use GetOverlayControls to examine which controls are already on the overlay. The returned UIElements can then be queried for their size and placement information [on the overlay]. For example, perhaps you have a preferred placement and prior to adding your control you want to detect if a control (perhaps placed by Pro or another add-in) already occupies that "space". Based on your examination of the existing overlay controls, your logic could adjust your default position accordingly, alter ZOrder, etc. It is not intended that you cast the controls to their underlying type. Simply use them "as" UIElement. Cast to FrameworkElement also, if needed. If you do need reference to your control "later on" you should hold a reference to it. We will update the API reference for AddOverlayControl and GetOverlayControls for 2.4 ... View more

Hi Karen, So somewhere along the line I am thinking you saw "Map.GetSelection()" - perhaps in a sample - and decided on that as "the" way to go. In your case, I would suggest selecting directly off the layer - "parcels" - instead. Similar to arcobjects, feature layers support both a Select and a Search method - the select will highlight the features on the map whereas search does not and applies the selection to the underlying feature class (with no visible highlight). To retrieve the list of layers from a Pro map or scene use the method "GetLayersAsFlattenedList" which I show below. I also encourage you to google "LINQ expressions" and read a few tutorials on it - the syntax can be a little intimidating at first - a lot of the Pro SDK samples use LINQ as it is the preferred technique for selecting items from a .NET collection. The most common LINQ methods are "Where", "FirstOrDefault", and "OfType". In the code below, I use the Pro SDK method "GetlayersAsFlattenedList()" on the Map, which I mentioned above, to return the collection of the map's layers. I then use a LINQ expression "FirstOrDefault" and that funky "lambda" syntax "lyr => lyr.Name ..." to select, from the returned list, either the first layer with a matching name of "parcels" or null (that is the purpose of "FirstOrDefault"). The final code looks like this:   var parcels = MapView.Active.Map.GetLayersAsFlattenedList().FirstOrDefault(lyr => lyr.Name == "parcels") as FeatureLayer;   if (parcels == null)         return; //parcels not found   await QueuedTask.Run(() =>   {     var sf = new SpatialQueryFilter()     {       FilterGeometry = geometry,       SpatialRelationship = SpatialRelationship.Intersects,       SubFields = "*"     };     var select = parcels.Select(sf);     var rc = ((FeatureLayer)parcels).GetSelection().Search();     while(rc.MoveNext())     {       var feature = rc.Current as Feature;       var pin = feature["PIN"];       //etc       ... ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ To help you answer these questions: //NEED: Populate form with "InVillage" value from Village Boundary layer ... //NEED: Populate form with "StreetID" from closest street segement from Streets layer I suggest the following sample to help you with understanding how to populate a form: DockpaneSimple sample It will introduce you to something called MVVM and how to add properties to your dock pane view model that get displayed on your dock pane view. Finding the nearest feature can be quite complicated. Geoprocessing has Proximity tools and spatial joins are also possible. You could also use a brute force approach progressively selecting on the street layer with an incrementally increased buffer applied to your selection geometry and then filter the "hits" for the closest feature (see ProSnippets Geometry#nearest-point-versus-nearest-vertex) ... View more

Mody, to answer the question of how to use a user control "within" a user control I recommend doing a google on "WPF DataTemplate" and "WPF ContentPresenter" and going on stackoverflow- You will find lots of examples there. To help you get going here are three options I put together but there many different permutations and possibilities in WPF...you will need to evaluate which is best for your situation. Alright, so, that said, assume this is your control (xaml not shown) public partial class ModyView : UserControl {‍ Option 1. Simply add a reference to it in your dockpane. This is the easiest: <!-- this is your dockpane --> <UserControl x:Class="ModyAddin.TheDockpaneView"              ...              xmlns:local="clr-namespace:ModyAddin"> <Grid>    <Border Background="..... >      <!-- In the dockpane xaml (i.e. the view) reference your user control -->      <local:ModyView x:Name="ModyViewControl" Margin="3,4,3,4" />‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Option 2: Use something called a content presenter. A content presenter is basically a placeholder into which you can put any content - in this case your user control. Bind it to a property of type UserControl or FrameworkElement (or even "ModyView" - our specific custom UserControl type if you prefer)... <!-- this is your dockpane --> <UserControl x:Class="ModyAddin.TheDockpaneView"              ...              xmlns:local="clr-namespace:ModyAddin"> <Grid>    <Border Background="..... >      <!-- In the dockpane xaml (i.e. the view) add a content presenter -->      <ContentPresenter Content="{Binding UserControlContent, Mode=OneWay}" /> ‍‍‍‍‍‍‍‍‍‍‍ and in the dockpane view model....when we set the property, the content will be shown. internal class TheDockPaneViewModel : DockPane‍ {   //the property in the binding - can also use FrameworkElement as the type   private UserControl _content = null;   public UserControl UserControlContent {          get { return _content; }          internal set { SetProperty(ref _content, value, () => UserControlContent); }   }   //usage...set the property during runtime...   _myDockPane.UserControlContent = new ModyView();‍‍‍‍‍‍‍‍‍‍‍‍‍ Option 3 Assume you have a non-visual class that you want to set as the content and you will be using your user control to render it. For example, a non-visual class called "StatusRuler"... public class StatusRuler {    public string Title { ...    public int Step { ....    public bool Completed { ...    ‍‍‍‍‍‍‍‍‍‍ The dockpane has a content presenter the same as option 2 but we now bind it to a property of type of "StatusRuler" (see the bottom code window)....the non-visual class....rather than a user control directly. This is our updated dockpane. internal class TheDockPaneViewModel : DockPane‍ {   //the property in the binding - set to a non-visual type   private StatusRuler _ruler = null;   public StatusRuler StatusRuler {          get { return _ruler; }          internal set { SetProperty(ref _ruler, value, () => StatusRuler); }   }   //usage...set the property during runtime...   _myDockPane.StatusRuler = new StatusRuler();‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Next we add a data template to the dockpane view - a data template links or associates our user control "ModyView" with the non-visual type "StatusRuler". Usually, the data template goes in your dockpane resources but it can go in a separate resource dictionary or even the resources of the ContentPresenter itself. It just depends on whether the data template is something you want to re-use on multiple dockpanes (without copy/pasting) or not. When you set the ContentPresenter to be an instance of the non-visual type "StatusRuler", the data template kicks in to tell the ContentPresenter to use an instance of the user control "ModyView" to show it. Et voila. <!-- this is your dockpane --> <UserControl x:Class="ModyAddin.TheDockpaneView"              ...              xmlns:local="clr-namespace:ModyAddin"> <UserControl.Resources>   <ResourceDictionary>     <DataTemplate DataType="{x:Type local:StatusRuler}">          <local:ModyView />     </DataTemplate> ... <Grid>    <Border Background="..... >      <!-- In the dockpane xaml (i.e. the view) add a content presenter -->      <ContentPresenter Content="{Binding StatusRuler, Mode=OneWay}" /> ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more