Bug 108149 - Impress Animation Error
Summary: Impress Animation Error
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
5.2.7.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Object-Animations
  Show dependency treegraph
 
Reported: 2017-05-27 08:29 UTC by WangYi
Modified: 2021-11-13 10:01 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
This pptx has animations errors that I described on bug details. (51.56 KB, application/vnd.openxmlformats-officedocument.presentationml.presentation)
2017-05-28 15:22 UTC, WangYi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description WangYi 2017-05-27 08:29:02 UTC
Description:
Hello.

I made the pptx document from MS Office Powerpoint 2013.
and I added some animations(such as Roate, Bounce, Teeter, Grow/Shrink, Underline, Bold Flash, Bold Reveal, Waves) to this pptx document on MS Office Powerpoint.
(I was going to attach the pptx file on this bug report, but there is no attaching function.)
But If I open this pptx document in LibreOffice Impress, the animations are very strange and shows me a lot of animation bugs.
Please check these errors and I want you to send email after resolve these issues.

Thanks.
Best Regards.

Steps to Reproduce:
1. Create pptx file on MS Office Powerpoint 2013.
2. Create some objects and give them some animations as follows.
Roate, Bounce, Teeter, Grow/Shrink, Underline, Bold Flash, Bold Reveal, Waves and so son.
3. Save that file on MS Office Powerpoint.
4. Run LibreOffice Impress and Open that pptx file.
5. Press the 'F5' on Keyboard and Check the animations.
6. You can see a lot of animation bugs.

Actual Results:  
All Animations have a lot of bugs and don't work well. 

Expected Results:
Animations must work same as MS Office PowerPoint 2013


Reproducible: Always

User Profile Reset: No

Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
Comment 1 Aron Budea 2017-05-27 17:47:46 UTC
There's an "Add an attachment"  link above the comment text box, please use that to add an attachment (there's a 10MB limit per file).
Comment 2 Buovjaga 2017-05-27 18:34:19 UTC
Please also search for existing reports about the animations.
Comment 3 Xisco Faulí 2017-05-27 23:53:03 UTC Comment hidden (obsolete)
Comment 4 WangYi 2017-05-28 15:22:19 UTC
Created attachment 133669 [details]
This pptx has animations errors that I described on bug details.
Comment 5 WangYi 2017-05-28 15:38:59 UTC
(In reply to Buovjaga from comment #2)
> Please also search for existing reports about the animations.

Thanks.
Can you tell me exiting reports which can give me great answer?
Comment 6 Buovjaga 2017-05-28 16:04:55 UTC
(In reply to WangYi from comment #5)
> (In reply to Buovjaga from comment #2)
> > Please also search for existing reports about the animations.
> 
> Thanks.
> Can you tell me exiting reports which can give me great answer?

https://bugs.documentfoundation.org/buglist.cgi?component=Impress&list_id=701814&query_format=advanced&resolution=---&short_desc=ppt%20animation&short_desc_type=allwordssubstr

At least Rotate is reported before.

Each one of those animations should have its own report. So you can go through that list and then create new reports for all the ones that are not yet reported.
Comment 7 Buovjaga 2017-06-03 05:43:09 UTC
Ok, I did some research on what animations are already reported.

Rotate: bug 99617
Grow/shrink: bug 98477
Lightspeed: bug 50499
Bounce: bug 45490
Fly in: bug 67348

So you can create reports for all the others that do not work and attach example files to each (having only one animation).
Comment 8 Xisco Faulí 2017-11-14 10:46:14 UTC
Hi WangYi,
Based on your document, i've created different reports for each animation. See metabug 109362. I guess we can close this one as duplicate of that one. Thanks for the document

*** This bug has been marked as a duplicate of bug 109362 ***
Comment 9 Aron Budea 2021-11-13 10:01:01 UTC
Let's use state INVALID, since it's more proper.

WangYi, several related bugs have been fixed since the report, please consider retesting with a recent version, and opening separate reports on individual issues as advised in comment 7.