<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - UI: PNG export dialog has radio button doesn't allow 'dimensions' or 'DPI' to be set both" href="https://bugs.documentfoundation.org/show_bug.cgi?id=144195#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - UI: PNG export dialog has radio button doesn't allow 'dimensions' or 'DPI' to be set both" href="https://bugs.documentfoundation.org/show_bug.cgi?id=144195">bug 144195</a> from <a class="email" href="mailto:xordevoreaux@gmail.com" title="xordevoreaux@gmail.com">xordevoreaux@gmail.com</a> <pre> > Here is the answer: > <a href="https://design.blog.documentfoundation.org/2016/04/01/the-many-faced-god">https://design.blog.documentfoundation.org/2016/04/01/the-many-faced-god</a>- > part-2-how-libreoffice-draw-is-expected-to-evolve/ > I'd like to add my 2 cents regarding that document that's more than half a decade old, times change, and the bugs I lodge against LO Draw probably would never have been issues, or even ever crossed the minds, of end-users in 2016. In 2016, LO draw didn't have fuzzy shadows, glowing effects, or several other features that it has today. Did anywhere in that half-decade document call for such? Can we put ancient documentation aside and the locked-in mentality that goes with it and look toward the future? Because I've a whole list of approved enhancements waiting in the wings for a programmer to pick up eventually, and I've love for one day for those to be incorporated DESPITE not being in that ancient document. Thank you.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>