Progressor Behavior in Custom Geoprocesses

Question

Morning folks,

Odd one for you. I'm trying to set up a progressor for a custom geoprocess that iterates through a large polygon feature. Problem is, I'm calling other arcpy tools with each iteration (specifically select by attributes, clip, and calculate geometry) and the progressor for those tools makes it so that you can only see the custom progressor for a split second in each iteration.

Is there any way to suppress these default progressor messages while a custom progressor is active?

Many thanks,

- Joshua

Hornbydd · Answer

☹️ Ah OK, thanks for getting back. At least your question identified the issue. I could not work out why 90% of the time my progressor bar would work and 10% of the time it didn't. In those "10%", I'm like you, part of my script tool makes calls to the select by attributes tool, which you had identified as the cause of the problem.

Joshua_Petitmermet · Answer

Afraid not, I ended up abandoning the progressor entirely and just tracking progress manually via AddMessage().

Hornbydd · Answer

Joshua,

Did you find a solution, I'm suffering the same issue?

Duncan