Latest Contributions by DavidHowes

On running a geoprocessing tool, show the results messages in a new dockable Geoprocessing Messages pane, which includes associated functionality. Despite their importance, accessing results messages is inefficient. When a geoprocessing tool is executed using the Run split button, the messages appear on the third tab of a popup Details window. A user has to click on the View Details link button, click on the Messages tab button, and, more often than not, resize the window. When re-running a tool from the History pane, the View Details popup is shown in hover mode when hovering over a result item, but the Parameters tab is shown by default. A user has to open the Messages tab and, often, resize the window, with a strong chance that the popup will disappear unless they pop out the window first. Accessing the View Details popup via the History item context menu is not much more efficient. Having to repeat the steps described above to access messages is unnecessarily cumbersome, especially during iterative tool development. A Geoprocessing Messages pane would significantly improve the user experience. The pane could remain open and, when a tool is run, existing messages could be replaced by new messages. Options could be provided to display parameter and environment details, but the main focus would be on messages. It may be useful to allow a user to choose between replacing messages or adding messages to a log, which could be exported to a text file. Such a log would be helpful for saving a record of a tool run or set of tool runs. Parameter and environment details could be included, but, again, the primary focus should be on messages. The View Details menu option for History items could be retained, although it would be helpful if there was an option to always show the Messages tab by default, rather than showing the Parameters tab. If adding a new dockable Geoprocessing Messages pane is not possible, it would be useful if .NET developers had access to the geoprocessing history and relevant events so that they can create their own messages pane. As a minimum, access to the collection of history items and an OnGeoprocessingToolFinishedEvent handler would be helpful. The developer could then get the messages and load them into a control of their choosing. ... View more

Update the SnapResult class to distinguish between three points: - the click point; - the point to which the click point is snapped if it lies within the snapping tolerance area; - the point to which the click point would be snapped if it were to lie within the snapping tolerance area. Here's why: SnapResults are provided in the OnSketchCompleteAsync event handler. If the click point is snapped to only one feature point - the geometry provided to the handler is set to the snap point - the first SnapResult object will provide -- Layer -- OID -- SnapLocation -- SnapType where the SnapLocation is equal to the geometry location. If the click point is outside the snap tolerance area - the geometry will represent the click location - Layer will be empty - OID will be -1 - SnapLocation will be the point to which the click point would be snapped if it were to lie within the snapping tolerance area - SnapType will be None It's confusing to use the SnapLocation property in two different ways. What the SnapResults say in the second case is that no snapping occurred, but here's the snap location. Furthermore, knowing the click location is sometimes helpful, but there may be no way to get it because handling the MouseDown event causes OnSketchCompleteAsync not to fire. Updating the SnapResult class properties as follows would provide greater clarity along with the three potentially useful locations: - Layer - OID - ClickPoint - SnapPoint - PotentialSnapPoint - SnapType where, using the descriptions from above, - ClickPoint is the click point, - SnapPoint is the point to which the click point is snapped if it lies within the snapping tolerance area, and - PotentialSnapPoint is the point to which the click point would be snapped if it were to lie within the snapping tolerance area. Note that "Point" is clearer than "Location" to describe what the corresponding property provides. No new computation is required. I'm simply asking that the captured and computed point locations are made available and clearly distinguished. ... View more

Adjust the startup option Options/Application/General/Start ArcGIS Pro/With a default project. Replace the textbox for the path with a combobox containing recent project paths. The user may then select a path or specify a new one by entering text or using the browse function. ... View more

Add a new startup option: Options/Application/General/Start ArcGIS Pro/With the last project This would save the user having to keep changing the default project path or choosing the project to open on every startup. ... View more

In the Catalog View and Catalog Pane, in the context menu for any item that includes tabular data, add direct opening options, such as - Open Table - Add to Current Map and Open (for Pane) - Add to <map name> and Open (for View) ... View more

Unless I'm missing something, obtaining the full path to a Catalog item appear to be inefficient. The options are: * For a layer source - Open the Layer Properties/Source page - Copy the Database value - Copy the Name value - Concatenate the two values - For a shapefile the full path is displayed, which is ideal * For a Catalog View or Pane item - Select the item - Open the Map ribbon - Click on Copy Path * For a Catalog View item - Copy the container path from the path textbox - Copy the name of the item - Concatenate the two values This could be simplified as follows: * On the Layer Properties/Source page - Include a Path row, providing the full path to the source item (as for a shapefile) * In the Catalog View - Show the full path for the selected item in the path textbox * In the Catalog Pane - Add a path textbox at the top of the Project page - Display the full path for a selected item * In the Catalog View and Catalog Pane - Add "Copy Path" to the context menu for all applicable catalog items (it was available for a few items in a previous release, but was then removed) - Allow a user to paste a full path for an item into the path or search textboxes and hit enter to expand the tree and select the item ... View more

For reasons I don't understand, I've been informed that my 12/24/20 post was my first post. If so, that makes my previous post my 0th post and potentially invisible, so I'm posting it again. Sorry if that's against the rules, If it is, it's fine to delete it. Situation ArcGIS Pro allows the user to set the default project to be opened on startup by specifying a path in Options/Application/General/Start ArcGIS Pro/With a default project Suggestion Add a shortcut on the Open/Recent projects list to specify the default project. This would work as follows: Under Project/Open, for each item the in the Recent Projects list, provide a second context menu item "Set as Startup Project" On click, set the default project value in Options/Application/General/Start ArcGIS Pro using the selected path ... View more

ArcGIS Pro 2.7 includes a new Resources section on the Start page. However, if a default project is set, a user may never see this page. In this situation, there appears to be no way to access the Resources section within ArcGIS Pro other than to change the Start ArcGIS Pro option to "Show the start page" and restart the program. It may be helpful to add a backstage Resources button and page to provide access to the information. ... View more