Description: On slides in Screen 16:9 format, the movement paths are compressed vertically. Steps to Reproduce: 1. Create object 2. Add effect Motion Paths:Circle Actual Results: On slides in Screen 16:9 format, the movement paths are compressed vertically. Expected Results: As with Screen 4:3 format Reproducible: Always User Profile Reset: No Additional Info: Версия: 6.3.2.2 ID сборки: FreeBSD ports 6.3.2_1 Потоков ЦП: 2; ОС:FreeBSD 12.1; Отрисовка ИП: по умолчанию; VCL: gtk2; Локаль: ru-RU (ru_RU.UTF-8); Язык интерфейса: ru-RU Calc: threaded
Reproduced, already in 3.3.0 (tested on Win 10) Arch Linux 64-bit Version: 7.1.0.0.alpha0+ Build ID: 8ff2889f417fdf9a2a2b849189dfd4e693bb7a45 CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: kf5 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 13 September 2020
This is not limited to the circles, but all motion paths. Most visible for the symmetrical paths, like circles, n point stars, equal triangles, etc. With the default Impress templates changed to 16:9 now, I'd argue the severity of this bug is higher than "minor".
Remember that minor means "the bug makes it substantially harder to make high quality work or requires users to not use some features": https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg
(In reply to Buovjaga from comment #3) > Remember that minor means "the bug makes it substantially harder to make > high quality work or requires users to not use some features": > https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart. > jpg I know changing the severity doesn't mean anything if no one plans to work on it, and I never intended to press this issue. But I'll just note that currently, it seems there is no way in UI to make the path with exact 1:1 height-width ratio (like entering the exact height and width dimension), and the user has to drag it by hand and judge by eyes. It's pretty close to "prevent users from making professional quality work" to me.
Dear JBrown, 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