Has any one see this issue before (See attached)? A coworker showed me this issue on his computer in the ArcMap Legends Properties window, it looks like some the buttons are cut off, Kind of like the text and objects in the Legends Properties are not scaling properly and are getting cut off by the size of the window, plus I dont think you can resize the properties windows. I am not sure how to tackle this issue, is it a configuration issue, system issue, Windows issue? Any suggestions would be helpful. We are on Desktop 10.6.1
Solved! Go to Solution.
This problem is caused by the monitor resolution settings. Take a look at this Support article: https://support.esri.com/en/technical-article/000007346
Cause
The monitor screen resolution is less than 1024 pixels in width, such as 800 by 600 pixels.
Solution or Workaround
Reset the the screen resolution to at least 1024 pixels in width.
Note: For this solution to be effective, make sure the font size is set to a size smaller than Large/150 DPI.
- Right-click anywhere on the Windows desktop and select Properties.
- Click the Settings tab.
- Move the screen resolution slider so the first value is 1024 pixels or higher. Esri requires a screen resolution of 1024 by 768 pixels or higher.
- Click Apply to save the changes, and click OK to exit.
This problem is caused by the monitor resolution settings. Take a look at this Support article: https://support.esri.com/en/technical-article/000007346
Cause
The monitor screen resolution is less than 1024 pixels in width, such as 800 by 600 pixels.
Solution or Workaround
Reset the the screen resolution to at least 1024 pixels in width.
Note: For this solution to be effective, make sure the font size is set to a size smaller than Large/150 DPI.
- Right-click anywhere on the Windows desktop and select Properties.
- Click the Settings tab.
- Move the screen resolution slider so the first value is 1024 pixels or higher. Esri requires a screen resolution of 1024 by 768 pixels or higher.
- Click Apply to save the changes, and click OK to exit.
to follow up, we ended up following this technical article to resolve our issue,
https://support.esri.com/en/technical-article/000012643
TY!