Latest Contributions by WilliamBuerger

The background geoprocessing concept can be useful in some cases.  In ArcPro, all geoprocessing is background.  I can get where ESRI is going with this.  But, in most cases, when I'm running some processing, I'm waiting for that to finish before I move on to something else.  I like to see the details of what is happening as well so I almost always hit the View Details button after starting a tool.  It would be nice if there were an option to show this by default.  Then, in the few cases were I do want to hide this while I do something else, I can just close it and let it continue to run in the background.  Although even than, I would likely just want to move the details off to the side so I can keep an eye on it while doing other things. Is there any option for this that I just haven't noticed?  If not, it would be a nice feature. ... View more

We're trying to hyperlink in ArcPro to some documents that have a single quote/apostrophe in the path.  Clicking the link gives the error... Any attempt to escape the character doesn't change the error.  I've tried double single quotes and %27 and it still gives the same error.  The fact that %27 gives the same error suggests that it reads the urlencode correctly and makes it a single quote before passing it on to whatever causes this error.  Anyone know how to get around this?  The obvious work around is to rename the folders to not have single quotes in them.  But single quotes are valid characters in normal urls.  So this seems to be a bug in the way Pro handles this. ... View more

I've know that some of our custom tools occasionally run into memory leaks from time to time.  Usually, we just run the tool in smaller batches to get through it.  But after doing some investigation, I finally tracked down where the problem is coming from.  It would seem that calling IFeatureClass.GetFeature or IStandaloneTable.GetRow on a table that is currently being edited, causes the row to not be released.  I tried using Marshal.FinalReleaseComObject to force it to release the feature but it didn't help.  I think I had some minor success or improvement by doing that and forcing garbage collection.  But it didn't fix everything.  If you do the same thing on a table that is not being edited, there's no issue.  Maybe there's something in the editor extension that is grabbing on to features that are being retrieved and not letting go of them. Here is some sample code I created that shows the issue.  It gets the OID of all of the features in the first layer in your map and puts them into an array.  Then goes through those OIDs and calls GetFeature for each one. var StartTime = DateTime.Now; var Count = 0; var Total = 0; var Layer = (IFeatureLayer)mxDoc.FocusMap.get_Layer(0); var Cursor = Layer.FeatureClass.Search(null, true); var OIDs = new List<int>(); var Feat = (IFeature) null; try {    while ((Feat = Cursor.NextFeature()) != null)    {       OIDs.Add(Feat.OID);       Total++;    } } finally {    Marshal.FinalReleaseComObject(Cursor); } foreach (var OID in OIDs) {    if (Count % 1000 == 0)    {       var Ts = DateTime.Now - StartTime;       MxApp.StatusBar.set_Message(0,          string.Format("{0:#,0}s - {1:#,0}/{2:#,0} - GetFeature()...", Ts.TotalSeconds, Count, Total));       Application.DoEvents();    }    Feat = Layer.FeatureClass.GetFeature(OID);    System.Runtime.InteropServices.Marshal.FinalReleaseComObject(Feat);    Feat = null;    Count++; } Attached is a video showing this code executing.  I've included Task Manager so you can watch the memory increase as it goes.  I've sped it up about 12x as it takes a few minutes to get through the whole thing.  If you run this with the layer not being edited, then there's no issue and memory usage never goes over about 200MB. ... View more