Bug 133517 - Object Animation: Exit: Boomerang distorts the object unexpectedly
Summary: Object Animation: Exit: Boomerang distorts the object unexpectedly
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: x86-64 (AMD64) All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Object-Animations
  Show dependency treegraph
 
Reported: 2020-05-30 08:25 UTC by JBrown
Modified: 2024-10-13 03:12 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description JBrown 2020-05-30 08:25:36 UTC
Description:
The size of the object and its path changes unexpectedly.

Affect:
Exit:Boomerang, Exit:Bounce, Exit:Magnify, Exit:Center Revolve.

Steps to Reproduce:
1. Create text object
2. Add effect Entrance:Boomerang
3. Add effect Exit:Boomerang (Start>After Previous)
4. Run the animation

Actual Results:
When animating an Exit:Boomerang effect, the size of the object changes unexpectedly.

Expected Results:
The effect of Exit:Boomerang should be the opposite of Entrance:Boomerang.


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
Comment 1 Buovjaga 2020-10-08 12:08:32 UTC
Reproduced

Arch Linux 64-bit
Version: 7.1.0.0.alpha0+
Build ID: a16f2d2bc1865dfbf8e755e683624843337c59da
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 7 October 2020
Comment 2 Buovjaga 2020-10-12 16:18:28 UTC
Already distorts in 3.3.0
Comment 3 QA Administrators 2022-10-13 03:32:04 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2024-10-13 03:12:33 UTC
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