Hi Kevin,
Thanks for your post. I've attempted to reproduce what you're describing and haven't seen the same behavior, but I think performing a screen share with Support is definitely a good way to investigate the environment, maps, data, etc.-- especially if you've ensured snapping is enabled, etc. I've looked into your open case and it looks like the analyst reached out to you yesterday via email for a convenient time to call, but I've since asked that an analyst call you to follow-up.
Thanks again!
Kirsten
Oh, thank you...I suspect my email may be out of date. I will check that now.
I am experiencing this same exact issue. Closing out the application and re-launching it seems to solve the problem. But this work around is a serious productivity killer.
Roberto,
Sounds like it! I'd recommend you call support if you have a reproducible case of this so they can help out. We need to find a repro case so a developer can debug it here in Redlands.
I am not sure if this is coincidence but it seems like whenever snapping stops working, the following procedure seems to get it working again without having to close and restart.
Save edits
Clear selections
Go back to the home tab and use the identify tool
Go back to the edit tab and edit again.
Roberto,
Do you have a good consistent repro case for this behavior (snapping stops working)? The dev team would like to try to determine what's going wrong here.
Regards,
Jeremy W.
Unfortunately, no. It was kind of random. There was no specific trigger.
I am having the same problem, using version 10.2.2. desktop. It often seems to happen when doing something outside editing, like turning another layer on/off. The advice to re-start editing does work, but is very time-consuming, especially since I have to keep turning layers on/off in order to see them but not snap to them.
Having explored further, the snapping seems to work if the one being snapped to has already been saved - so 'save edits' between each new polygon.