Description: Suppose that you have multiple objects and that you group them into a single object. That resulting object should get an initial rotation angle at 0 (as shown by going in the "position and size" dialog and selecting the "rotation" pane. This is important to then allow the group-object to be accurately rotated at will in case there is need to do so. However, the grouping action in LibO results in the newly creating group object having an initial angle different from zero (and probably equal to the rotating angle of one of the objects put in the group). This unnecessarily complicates working with the group object (also because it is by no means clear what initial object it will inherit its initial angle from). For instance, consider the example in the attached file, where there are 3 objects (two circles and a line) making up the symbol of a switch. If you group the objects you get a switch symbol as a single object, but this immediately appears to have a 30° rotation angle even if the switch is horizontal! In fact, the compound object seems to take its initial rotation angle with the line object. This makes it unnecessarily complex to use the newly generated symbol (e.g. to rotate it to be vertical). In the proposed example things are really not to bad, because 30 is a round number. Yet if it was 29.7 making the compound object perfectly vertical, could be a bit hard. Furthermore, things get really weird when you put objects on the gallery. You may then end up picking something in the gallery, seeing it "horizontal" or "vertical" and then find out that for LibO it is neither. I think that LibO should "reset" the initial rotation angle when creating a group object. I believe that this bug is inherited from OO but cannot really check. Steps to Reproduce: See description and test case Actual Results: See description and test case Expected Results: See description and test case Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: DrawingDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes
Created attachment 150542 [details] test case
confirm in Version: 6.3.0.0.alpha0+ Build ID: d31d77b7199ecc9a7edc899d9703e9da52d5cbd1 CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-04-01_00:04:09 Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded
Dear sergio.callegari, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear sergio.callegari, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug