<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Add button in tabbed mode" href="https://bugs.documentfoundation.org/show_bug.cgi?id=121556#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Add button in tabbed mode" href="https://bugs.documentfoundation.org/show_bug.cgi?id=121556">bug 121556</a> from <a class="email" href="mailto:tietze.heiko@gmail.com" title="Heiko Tietze <tietze.heiko@gmail.com>"> Heiko Tietze</a> <pre>(In reply to Drew Jensen from <a href="show_bug.cgi?id=121556#c3">comment #3</a>) > I would of thought you would prefer to change the summary to deal with how > to launch the Customize dialog since that seems to have slipped through the > cracks during the time this feature was in experimental stage. > > Seriously since there no such thing, that I can see, as requirements > documents any longer Bugzilla is the only thing you have to track > requirements and the UI for getting to the Customize Dialog is a requirement. Don't see why standard toolbar or notebookbar would need direct access to the customization. This feature is not so often used that it needs to get exposed on the primary UI. And we should also not just duplicate the standard toolbar, so the on-the-fly customization (button on/off) is just not available. It was/is a vehicle for the standard toolbar to circumvent the inconvenient customization that was improved greatly in the last release. But the last piece in the request, the customization in general, is required and has a duplicate.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>