Latest Contributions by CharlesMacleod

As Uma stated >>The Pro UI is written using WPF<< and the SDK templates automate the generation of most of the possible UI elements that are supported in Pro (buttons, tools, panes, dockpanes, property pages, property sheets, custom controls, and so on). However, you can write any of the UI elements by hand - you would just be responsible for deriving from the correct base classes, adding the requisite overloads and so forth, and adding the necessary Config.daml entries.  This can be a tedious business to repeat each time you need to add, say a button or a dockpane. That is where the SDK templates come in - to help automate a lot of these repetitive tasks. However, you don't _have_ to use them. You can do it all by hand as you need (for example - copy/pasting or moving existing classes from one add-in project to another). Also, within WPF, the underlying technology used by the Pro UI, you can host a Winforms control within a WPF user control or window - though this is not a common pattern and is usually done for legacy reasons (eg an old WinForms control provides a specific set of functionality not easily duplicated in WPF or the level of effort is too great to rewrite it). You can read the  Microsoft documentation on WindowsFormHost for more information if you are interested. ... View more

Ideally, you want the defaultAssembly and defaultNamespace attributes to _match_ the corresponding properties in your visual studio project (i.e. Application properties tab, Assembly name, Default namespace). If you change the name of your assembly or default namespace in Visual Studio then be sure to update your Config.daml to keep it in sync. Additionally, depending on how you have your project arranged and which project folders you organize your content into, you may also need to change the className attribute on your various DAML entries if you rename classes or move them around. If a given control or dockpane or whatever is _not_ in the default namespace then you must always fully qualify the className attribute. The SDK templates do this for you automatically when they first generate a given DAML entry but if you refactor your add-in content then it is your responsibility to keep your Config.daml up to date. In your example, say you were to refactor your Module cs file to a different namespace (or rename it or....) then you would need to go into the Config.daml and change the "<module className" attribute to match - fully qualifying the className if your "refactored" ModuleMain were to no longer be in the MyCompany.MyDepartment.MyAddin namespace (i.e. your current default). ... View more

This section of the Pro Concepts Framework may help: ProConcepts-Framework#module-plug-in. This is basically what Than is describing. Some debugging tips are here: ProGuide-Diagnosing-ArcGIS-Pro-Add-ins ... View more

I think we have two separate things going on here and please confirm: 1) You originally were asking can you specify a clipping polygon for the map via the API, is that right? The answer is no. You cannot and this will be added for 2.6 2) You are using EditOperation.Clip to "manually" clip features and you have encountered a bug, is that right? So no, my statement regarding 1) , map clipping, is not related. To submit a bug please contact tech support. This post may help: How to report a bug in ArcGIS Pro Note: just looking at your code above, I believe the result you are looking for requires ClipMode.PreserveArea not DiscardArea. ... View more

In general, calling a modal dialog from the queued task should be avoided. protected override void OnClick() { //construct on the UI var dlg = new SaveItemDialog(); dlg.Title = "On QueuedTask"; QueuedTask.Run(() => { FrameworkApplication.Current.Dispatcher.Invoke(() => { var result = dlg.ShowDialog(); }); }); } ....‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

Overlays are not persisted which is why you cannot print (or export) them. At 2.6 there will be the concept of a graphics layer. Graphics you add to a graphics layer will be persistable (and so can be printed). ... View more

Jamal, yes, I investigated this and setting clipping on the map is not currently possible via the API. I have passed on the requirement to the mapping team. It will be targeted for release at 2.6 ... View more

Hi Simon, as I mentioned earlier, the active portal remains the active portal even if you programmatically connect to a different portal and there is only one portal active at any given time. You could try to search and retrieve item content via portal methods from your non-active portal...and then use MapFactory.CreateMapFromItem or LayerFactory.CreateItem overloads that consume Item (depending on what the content is). ... View more

No. The active portal will remain the active portal ... View more

Assuming you have a portal instance (eg via GetPortal from the ArcGISPortalManager), you could use its SignInAsync method to sign in. This will prompt for credentials with the sign-in window unless they have been previously cached (eg, via a preceding connection). If you need a token for REST requests then call GetToken to get the token. ... View more

At 2.5, a new Invalidate method has been added to the MapView. The first call would invalidate the entire layer. Pass in an extent to limit invalidation to just a particular area. The second call will invalidate the extent of the features whose oids are in the lists for the two layers. Invalidate(Layer,Envelope) Invalidate(IReadOnlyDictionary<Layer,List<long>>) MapView.Active.Invalidate(someLayer, null);‍‍‍‍‍ var dict = ... dict[layer1] = new List<long> { 20,21,31, ...}; dict[layer2] = new List<long> { 20,21,31, ...}; MapView.Active.Invalidate(dict);‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more