10/11/2019 9:17 AM | |
Joined: 2/28/2013 Last visit: 8/29/2024 Posts: 32 Rating: (0) |
Georg: I have already guessed that this setting is from the Windows OS but somehow the way WinCC is reading those settings must have changed between V7.5 and old versions. As I have mentioned in V7.4 SP1 on Windows 7 and 10 I get the same offset. In V7.5 on Windows 10 I get a different offset - all OS settings are the same (default) EMurias: Thanks for the hint - did you already figure out how WinCC is reading those values? I wonder if I can predict the offset of the Popup somehow. PS: I added an attachment with 3 screenshots displaying the situation. The WinCC project is on all 3 systems the same - no additional settings have been made in the OS settings, everything is default. AttachmentBorderPictures.zip (299 Downloads) |
Last edited by: MAB_cc at: 10/11/2019 10:10:36Last edited by: MAB_cc at: 10/11/2019 10:10:48Last edited by: MAB_cc at: 10/11/2019 10:11:15 |
|
11/5/2019 12:21 AM | |
Joined: 4/15/2012 Last visit: 6/24/2024 Posts: 2 Rating: (0) |
Yep We have the same problem when we upgraded from WINCC 7.0 to 7.5 on Windows server 2016. Problem is that these borders eat into the space used by the picture file that it calls and therefore masks some of the screen details ( Buttons etc.) Don't really feel like modifying all the screens. as there are hundreds of embedded screens. Any other fix from Siemens apart from modifying the registry? AttachmentAutomation.zip (259 Downloads) |
Follow us on