Got some results this time. When run, the tools chug away and the classic "Not Responding" shows up, but then it finishes out after several seconds.
Tool runs:
Check for Overlaps - worked when run on parcels with an intentional overlap. Looks good.
Check for Gaps - no results for output feature class GapErrors_poly when run on parcels with gaps, but did get the parcels gaps correctly depicted as lines in GapErrors_line output (purple lines below).
Check Line Segments - DangleErrors output correctly found two dangles that were close to other lines, but missed dangles that were far from other lines. Could be a just be a tolerance setting, though.
Unfortunately, no results for OverlapErrors_line output despite the intentional addition of line overlaps to the street test data.
Note - I made some assumptions when running these, which may influence the results:
1. The tools ran without being in Editing Mode for the selected feature class, which I assume is OK. If instead it is assumed that the user is in Editing Mode for the feature class being checked, let us know.
2. I didn't worry about whether the layers selected to run a tool on were set as specifically Selectable.
3. Ran the tools on test feature classes in a File Geodatabase. Did not try them on Versioned data.
Also, the bane of all software development, a feature request Is there a way to change the default location the output feature classes get written to? At the moment the seem to be going to a new geodatabase added to the C: drive. Not a critical request, but it would be nice to be able to save it to a few levels further out in the C: drive.
Looking good,
Chris Donohue, GISP