I have attached a screen capture of ArcGIS Pro behavior. In the short video I click the navigate tool (not shown) and press the shift key as it was my understanding that this would allow me to Window zoom in a part of the map that I am interested in.
Instead pressing the shift key causes the zoom of the layout to zoomout to infinity. Why is this happening? and why would anyone want it to happen? It is maddeningly frustrating. similar types of behavior occur when I try to use "Select".
This behavior seems to be limited to when the Layout is the activated
I also might add that similar to ArcGIS desktop behavior requiring some combination of pressing "C" or using the Shift key to reset the current tool; I seem perpetually stuck in a rotate view behavior that pressing "C" or "shift" doesn't seem to fix.
This behavior was submitted as the following bug:
BUG-000086476: The Zoom In, Zoom Out, and Pan tools from the toolba..
The additional information section explains the conclusion.
Additional Information
Esri has investigated this issue and found it to be caused by certain antivirus software. Please work with the users' antivirus vendor to determine the appropriate security settings to resolve interference with ArcGIS software.
Interesting. I'm running ArcIS Pro 2.1.2, inserted a new layout, inserted a new Map Frame, clicked Navigate, held the Shift key down and Pro zoomed in rather than continuous, infinite zoom out. Just a question - have you seen the
Keyboard Shortcuts for Layouts
shortcut page? Also, what release of ArcGIS Pro are you using?
We have a bug logged that
seems to be
related to having Webroot installed on the machine.
[BUG-000086476: The Zoom In, Zoom Out, and Pan tools from the toolbar become stuck in ArcMap after pressing the corresponding Z, X, and C hot keys.] I didn't want to just jump to that conclusion on this post before I heard back from one of you.
We're actively investigating this issue, but unfortunately, for now there is no listed workaround. I'm not familiar with Webroot, but is there a way to quickly disable it. At least for testing, you might disable it, work in Pro and see if it alleviates the behavior.
