nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Implementing better program feedback for the user

OliverHoehn

When ArcGIS Pro - e.g. due to slow connection speed/network speed - cannot access/read/write the user only gets a "spinning hourglass". The User doesn't know why/what is going on, or if the process is still running or if AGP has crashed.
Here a pop-up window with a description (what AGP is trying in the background) would be much better and helpful user feedback!

Further example: when loading large data sets/services etc, here a progress bar would be much more informative (as implemented in QGIS).

Find more posts tagged with

Usability (UI-UX)

Status: Open

Comments

KoryKramer

@OliverHoehn and others on this thread who experience this, have you tried using Diagnostic Monitor to narrow down what is causing the delay?

You mentioned loading a large dataset or service. If you run diagnostic monitor, look at the Log tab and sort on elapsed time to find the longest-running operations, is the delay in reading that data from a remote location?

I understand the idea is simply about adding more progressors when needed - but I thought we already had an 'Adding data...' progressor, so it will be helpful for anybody adding kudos or comments to this idea to work with Diagnostic Monitor and share specific examples of what is happening on your machine when you do not get a progressor.

Thanks!

OliverHoehn

hey Kory, yes the DM is kind of helpful for us IT-savvy GIS professionals. our users are mainly civil servants who use GIS as a tool to get a job done and don't want to check somewhat cryptic/sometimes generic monitor results. We learned from our users that better usability/user feedback in ArcGIS Pro would not only be extremely helpful to them knowing why they see a spinning hourglass but also increase acceptance working with ArcGIS Pro in the first place.

Thanks