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; } } }

Lock Geoprocessing inputs until the tool ready to accept typing

LoriEmersonKDOT

I'm tired of overwriting existing files because the Geoprocessing tools reset the output file name to what I had previously.

All geoprocessing tools take a long time to process each input field before it can accept anything in the next input field. Just freeze any other inputs in the tool until Esri's code can catch up. Poor coding. Pro seems on the surface to have more functionality, but is far inferior to ArcMap.

Finde mehr Beiträge mit dem Tag

Geoprocessing

Status: Öffnen

Kommentare

MargaretCrawford

Hi @LoriEmersonKDOT,

This sounds more like a bug. Could you provide a little more detail about the issue you are encountering? Maybe show a short gif or video of it, or describe the steps and how it occurs? Also, please let me know which version of ArcGIS Pro you are using.

LoriEmersonKDOT

I'm using ArcGIS Pro 3.2.1.

The problem occurs with all Geoprocessing tools. When I enter the input file, the four dots at the top start scrolling to show that it's thinking. If I don't wait long enough and enter the next parameter, such as the output file, it ignores what I just entered. Sometimes, the cursor jumps to the front of the parameter field while I'm typing.

RTPL_AU

There are many components of Pro (even in 3.3.1 on very high end hardware) that is sluggish and prone to miss mouse clicks or react to a mouse click on an object where the mouse position was a few ms before. Rapid typing and moves using TAB, etc also suffers from the GUI sluggishness, but a bit less in the things I do often.

I lodged BUG-000144222 but it was noted as 'not reproducible' and the feedback from Esri Inc was to 'work slower'!

EDIT - exact reply:

ALTERNATE SOLUTION

Pause with every operation to wait for the interface to catch up before placing the next click.

@LoriEmersonKDOTdon't feel alone.

@MargaretCrawford this is a real problem to those of us who work fast and it is very frustrating to continually have to pause to see if Pro has interpreted input correctly.

AlfredBaldenweck

I’ve encountered this as well. If you start your input before the tool’s validation methods (updateMessages(), updateParameters() or whatever their equivalents are) have finished running, the parameters get reset to what they should be when validation finishes. This makes sense, except for it can lead to multiple parameters having to be re-entered.

I don’t mega love this idea (Pro is entirely too fond of freezing your abilities arbitrarily— backups, reloading the map, applying a definition query,etc. Not the application itself freezing, but the map.) but I do see the need for this issue to be solved one way or another, and freezing input until validation is done is one way to do it. In some cases (or at least in my PYTs) this already happens.

The solution being “Work more slowly” is not viable.

Nehmen Sie an der Diskussion teil

Melden Sie sich an, um zu posten, Inhalte zu folgen und mehr. Neu hier? Kostenlos registrieren.