<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Multiselect Contextmenu for all apps" href="https://bugs.documentfoundation.org/show_bug.cgi?id=119526#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Multiselect Contextmenu for all apps" href="https://bugs.documentfoundation.org/show_bug.cgi?id=119526">bug 119526</a> from <a class="email" href="mailto:momonasmon@gmail.com" title="Maxim Monastirsky <momonasmon@gmail.com>"> Maxim Monastirsky</a> <pre>I have some concerns about it: 1. It doesn't seem like there are many commands that apply to multiple selection but not to a single object. In fact, I can't think of anything besides the group command (there is also align sub menu in Calc which doesn't work for a single object, but hopefully it will be implemented sooner or later - see <a class="bz_bug_link bz_status_NEW " title="NEW - Calc-Picture attached to cell- Can not controll place picture left/right/Center/Top/bottom etc" href="show_bug.cgi?id=100394">Bug 100394</a>). Having yet another context menu just because one or two special commands, doesn't sound like something that will make maintenance easier. 2. There are two kinds of multiple selection: (a) Where all the selected objects are of the same kind (e.g. two shapes). (b) Where the selected objects are of different kinds (e.g. a shape and a form control). I think that for (a) it still makes sense to show the context menu which is associated with this kind of object, and not some generic "multiselect" menu. The use-case is applying the same attribute to several objects at once, e.g. currently it's possible to select several form controls, right click -> Control..., and set a background color for all of them. To keep this possibility after introducing a "multiselect" menu, we will need to add the form-specific commands to that "multiselect" menu (and hide them dynamically if no form control is selected), as well as other commands related to all other possible object kinds, resulting in one big menu file. Is it really something we would like to do? Of course, we can still introduce "multiselect" menu for type (b) only, but then it won't allow us to remove commands related to multiple selection from the other context menus. So while we might consider such possibility by itself, it isn't something that can reduce maintenance.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>