<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - FORMATTING: FILESAVE: Writer compatibility setting doesn't save properly and keeps resetting unwanted option to be used" href="https://bugs.documentfoundation.org/show_bug.cgi?id=138544#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - FORMATTING: FILESAVE: Writer compatibility setting doesn't save properly and keeps resetting unwanted option to be used" href="https://bugs.documentfoundation.org/show_bug.cgi?id=138544">bug 138544</a> from <a class="email" href="mailto:ernest@bywater.net.au" title="Ernest Bywater <ernest@bywater.net.au>"> Ernest Bywater</a> <pre>(In reply to Justin L from <a href="show_bug.cgi?id=138544#c9">comment #9</a>) > (In reply to Ernest Bywater from <a href="show_bug.cgi?id=138544#c8">comment #8</a>) > > Please insert a Primal Scream of your choice here. > The default to "on" when user settings are not loaded with the document has > been true since at least 5.2. > > I am getting very confused by looking at this. mbUseVirtualDevice seems to > be the opposite of UsePtrMetrics (which defaults to false) - and yet > UseVirtualDevice seems to be the variable tied to "Use printer metrics for > document formatting". If it confuses you who can look at such things, just imagine how it confuses us poor users who can't get that deep into the code. I don't know when the code change occurred, I can only comment on what I observe of when it affected me and what I learn by checking things out. I only noticed the issue after I had to reload my OS due to a change of motherboard, and when I loaded LO 7 I had to rebuild all of my personal settings. It is possible that one of the settings changed from the default ones when I reloaded the software was done different his time, but I don't know for sure. Why the 2 settings mentioned in 19 Dec 2020 post are interacting the way they are is beyond me. It is something I suggest the developers try to work out as it may have other unexpected effects elsewhere that haven't yet been noticed or reported. I have found a way to get around the problem that concerned me, as I noted in that post, so I'm happy to be able to get on with my story writing and leave the head scratching to more knowledgeable persons like yourself.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>