Problem description: Multiple Select is not running with crtl or shift ??? Platform (if different from the browser): Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20100101 Firefox/13.0
Could you elaborate on that? Write steps to reproduce your problem? Where and when it happens?
I'm confused, this happens in "LibreOffice Writer" and not "LibreOffice Draw". In "LibreOffice Writer", you can not select multiple elements with the "Shift". Why?
(In reply to comment #2) > In "LibreOffice Writer", you can not select multiple elements with the "Shift". > Why? I created few text and callout fields in Writer. Then selected some of them with shift without problem.
But if you make frame, text-frame or insert picture or some object in writer you don't select mutliple element for a copy or align the objects together. (sorry for my english).
(In reply to comment #4) > But if you make frame, text-frame or insert picture or some object in writer > you don't select mutliple element for a copy or align the objects together. > (sorry for my english). I had no problems while selecting few object types you mentioned and aligning them. Could you attach any example documents where you have this problem?
Created attachment 63527 [details] exemple in writer
Confirmed with: LO 3.5.4.2 Build ID: own W7 debug build Windows 7 Professional SP1 64 bit Could not multi select with attached document. Similar to bug 35355.
Reproduced on Libo 4 Version 4.0.0.0.beta1 (Build ID: 87906242e87d3ddb2ba9827818f2d1416d80cc7) Ubuntu 12.04 64bits Work-around, clic on "First arrow" on draw toolbar, and drag a zone outside the objects to select, and then it works.
Created attachment 73043 [details] Another example of this bug that works in Writer 3.6.4.3 This is still a problem in: LO v. 3.6.4.3 Ubuntu 12.10 - 32 bits How can we get attention to this one? I can't believe there isn't more people in the CC list - maybe there is a dup with more people?
Oh. This is probably a duplicate of Bug 37960. Please join the conversation (or lack thereof) there. *** This bug has been marked as a duplicate of bug 37960 ***