Latest Contributions by CharlesMacleod

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

Barbara, this might help: https://github.com/esri/arcgis-pro-sdk/wiki/ProGuide-content-and-image-resources It covers the various options for referencing images in your add-in. Pay close attention to the "image" Uri syntax - in particular the "/" - is it forwards or backwards "\"...? Notice for AddinContent it is backwards "\".... One option that is not in that guide, but, seeing your post, I will add it, is to use something called a pack Uri. (cm - actually, on review, there is a section there called Referencing images from Arcgis Pro but I will expand it). A pack Uri is a way of referencing content that is contained, as a resource, ~within~ an assembly. A pack Uri looks like this <Button ... largeImage="pack://application:,,,/ArcGIS.Desktop.Resources;component/Images/GenericButtonBlue32.png">‍‍‍‍‍ (and is a bit unfriendly). If you choose to use a pack Uri from your ~own~ add-in (notice how this one references "ArcGIS.Desktop.Resources" which is the Pro assembly that contains all of the Pro icons) you would do the following: Add the image to your add-in project. Assume you add it to the folder called "Images". In Visual Studio, on the image properties, set its "Build Action" to Resource Change the pack Uri as follows - let's make an assumption that your add-in assembly is called "MyAddin.dll" and the image you added was called "MyImage32.png" and was added into the add-in Images folder: <Button ... largeImage="pack://application:,,,/MyAddin;component/Images/MyImage32.png">‍‍‍‍‍ One final point: After following these instructions your image may still not show (eg on the button). Why? Well, let's assume that the issue is not syntax, the issue is not incorrect Build Action or path or other user error. Everything is exactly correct but the image still does not show.... The answer is because of delay loading. Add-ins, by default, are delay loaded. This means that they do not actually ~load~ until a user activates them - usually by clicking on a button that is contained within the add-in. At that point in time, and only at that point in time, does the add-in assembly load. Delay loading is done as an optimization technique to only load those assemblies as they are needed....on demand, so to speak....and not all at once at startup. What this means for you is that the image you added as a Resource into your add-in assembly will not have been loaded (until the add-in is loaded) when the Pro ribbon is shown - In other words, you can "see" your button (sans image) but the add-in behind it is, in fact, not loaded and so neither are any of its resources - to include the button image!!!. Alright, well great....but I still need to know how do I get my image loaded and shown on the button on the ribbon! You have three options: Force your add-in to load at Pro initialization. In that case your add-in assembly will be loaded and the image will be immediately available. To do this set the module "autoLoad" property in your Config.daml to "true" (it is false by default). Reference an image in a dll that is loaded at start-up (such as the images found in ArcGIS.Desktop.Resources.dll) - Notice that this is what the Pro SDK Item templates do - by default all images are referenced from the Pro resources dll. Use AddinContent as the Image "Build Action". AddinContent is a custom build action specifically designed to deal with the delay loading characteristics of add-ins and is installed with the Pro SDK. In a nutshell, if you use "AddinContent ", the image will be referenced from within the add-in zip archive and not from within the assembly. In other words, Pro does not have to load the assembly to access the images built as "AddinContent". Note that the path separators for the image path point backwards "\". The downside with AddinContent is that Images with that build action type, because they live in the zip archive and not in the dll as resources, can only by referenced in the Config.daml and not in a WPF User Control, for example (via a pack Uri). It is a custom content type (we, "Esri" implemented to support delay loading) and is not a WPF resource type. Again, consult https://github.com/esri/arcgis-pro-sdk/wiki/ProGuide-content-and-image-resourcesfor more information and I will update that document to cover provide more details on use of pack Uris in the Config.daml. ... View more

Go to https://solutions.arcgis.com/defense/help/military-symbology-styles/ and download the latest version(s) (100.6). Yours looks to be quite old and pre-dates the use of Arcade, etc. ... View more

Note the instructions in steps 2 and 3 from the github: 2. Open the copy of the mil2525c.stylx in an SQLite database editor. 3. In the meta table, ....‍‍ So you will need a SQLite database editor. The one most people use is called "DB Browser for SQLite". Download and install it (or another one of your own choosing). Open the stylx file in the browser. Open up the "meta" table and change the value for "readonly" to be "false". ... View more

Hi Max, this has been added to 2.5. Look for "public static CreateProjectSettings GetDefaultProjectSettings();" on the Project class. Example usage: Project.CreateAsync( Project.GetDefaultProjectSettings()); ... View more

Hi David, your add-in Module still loads even if you have not enabled your add-in (via, I am assuming, an IExtensionConfig implementation?). Assuming you are using IExtensionConfig, your module always needs to load to allow you, the add-in developer, to respond to a licensing check from the Pro app (which is usually triggered when the user attempts to "check" or enable your extension via the licensing tab on the Pro backstage). This means that your add-in will autoload as normal, if that is what you specified in your config.daml, and can listen to the OnReadSettingsAsync callback regardless of its "State" returned from IExtensionConfig. Therefore, the add-in module can retrieve the stored defaults via the callback "as usual" whenever a project opens - even though, to the "outside" world, you may be showing its capabilities (tools, buttons, etc) as disabled. ... View more