<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Bounding box indicators are rendered erroneously on higher-resolution screen" href="https://bugs.documentfoundation.org/show_bug.cgi?id=116920#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Bounding box indicators are rendered erroneously on higher-resolution screen" href="https://bugs.documentfoundation.org/show_bug.cgi?id=116920">bug 116920</a> from <a class="email" href="mailto:rb.henschel@t-online.de" title="Regina Henschel <rb.henschel@t-online.de>"> Regina Henschel</a> <pre>I can produce a similar result, if I set the display to 200% (resulting in 192dpi) in the system settings of Window 10, although I have a normal monitor. The markers are contained in the files markers.png and cropmarkers.png in the folder svx/res in the images_???.zip file. Instead of ??? use the theme, you have selected. The needed markers are cut from that images. There is method CountDPIScaleFactor(sal_Int32 nDPI) in windows.cxx which generates a scaling factor. In my case of 192dpi it would generate 200%. I have taken the "cropmarkers" of an image as example. The resulting markers look as if the pixel offset, which is needed to cut the desired marker from the large image, is multiplied with this 200% and therefore the wrong part of the image is taken as "marker". Do you have a display resolution in Windows set, which is different from the normal 100%? Or is such value set by the device driver?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>