<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Repeated load/save/close cycles result in some drawing objects changing position over time." href="https://bugs.documentfoundation.org/show_bug.cgi?id=132050#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Repeated load/save/close cycles result in some drawing objects changing position over time." href="https://bugs.documentfoundation.org/show_bug.cgi?id=132050">bug 132050</a> from <a class="email" href="mailto:brianjheisler@gmail.com" title="brianjheisler@gmail.com <brianjheisler@gmail.com>"> brianjheisler@gmail.com</a> <pre>Thanks Regina! I "un-Mirrored" the large rectangle and the drift stopped happening. Unfortunately, when I mirrored the grouped object (something I have to do a lot when I use LO Draw) the drifting returned. I fear this will render the mirroring feature somewhat problematic. I can't say that I fully understand why the mirroring operation cannot notice when the "middle" of an object won't be the "true middle" of an object and drop to the right a half-step so it will be aligned as it was before the mirroring. The fact that the error here continually accumulates each time the position data is transferred from disk to ram then back to disk has me confused. The error should happen once (@ 1/2 resolution) then stop. Anyway... I've been experimenting with various combinations of mirroring (both individual objects and grouped objects) as well as rotating grouped objects. It appears that any mirroring - either at the object level or the grouped level - causes drifting with objects but these objects have to be of certain sizes. (Repositioning causes problems with the large rectangle but never the small rectangle... in this example.) I will attach a second demo file to show my results.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>