Select to view content in your preferred language

Traverse changes shape after completion

242
4
Jump to solution
02-28-2025 11:48 AM
ThomasGoodridge
Regular Contributor

I'm trying to draw easements using the traverse tool. The top picture is what it's supposed to look like. The bottom picture is what it does when I click finish. This is in Pro 3.4.0, and I've tried clearing the cache and restarting Pro, but the problem persists.

ThomasGoodridge_0-1740771218866.png

ThomasGoodridge_1-1740771280693.png

 

 

0 Kudos
2 Solutions

Accepted Solutions
Jordan_Brasher
Esri Contributor

Hi Thomas. Are you clicking the Finish button in the Traverse tool's pane or the one (with the green check mark) on the Edit toolbar? Do we see a difference in behavior when using one button versus the other?

View solution in original post

0 Kudos
Jordan_Brasher
Esri Contributor

Hi @ThomasGoodridge, thanks for letting me know. I see the behavior on my side as well. The following defect has been logged for this behavior.

BUG-000176312: When creating a polygon feature using the COGO Traverse tool, the Finish button in the tool's pane finishes the drawing differently than the Finish button on the Edit toolbar

View solution in original post

0 Kudos
4 Replies
Jordan_Brasher
Esri Contributor

Hi Thomas. Are you clicking the Finish button in the Traverse tool's pane or the one (with the green check mark) on the Edit toolbar? Do we see a difference in behavior when using one button versus the other?

0 Kudos
ThomasGoodridge
Regular Contributor

The editor checkmark worked, but the traverse button doesn't. Weird.

Thanks

0 Kudos
Jordan_Brasher
Esri Contributor

Hi @ThomasGoodridge, thanks for letting me know. I see the behavior on my side as well. The following defect has been logged for this behavior.

BUG-000176312: When creating a polygon feature using the COGO Traverse tool, the Finish button in the tool's pane finishes the drawing differently than the Finish button on the Edit toolbar

0 Kudos
JakeAdamsUGRC
Occasional Contributor

For what it's worth, I'm seeing the same behavior in Pro 3.3.0

0 Kudos