Description: Trigger on click, Shape is shown after animation Steps to Reproduce: 1. Open Game.odp (in the attachment). 2. Shape 1 has trigger Eit on click to it. 3. Set up Hide after animation. See screenshots. Actual Results: Shape 1 is shown after exit animation. Expected Results: Shape 1 should disappear at all. Reproducible: Always User Profile Reset: No Additional Info: Tested with Version: 7.0.0.0.alpha1 Build ID: 6a03b2a54143a9bc0c6d4c7f1... CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: kf5; Locale: ru-RU (ru_RU.UTF-8); UI: en-US Calc: threaded
Created attachment 160756 [details] scr1
Created attachment 160757 [details] scr2
Created attachment 160758 [details] Game.odp
Reproduced Version: 6.4.4.2 (x64) Build-ID: 3d775be2011f3886db32dfd395a6a6d1ca2630ff CPU-Threads: 4; BS: Windows 10.0 Build 18363; UI-Render: Standard; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: CL
Dear Vera Blagoveschenskaya, 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
Reproduced in: Version: 6.3.0.0.alpha1 (x64) Build ID: 547edd20e527fb02900f6174973770d26306e2e7 CPU threads: 6; OS: Windows 10.0; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: CL Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 676e0527d2f31556eccae314fbb12ce204f02ec7 CPU threads: 6; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Not reproduced in: Version: 5.4.0.0.alpha1 (x64) Build ID: 0b9f9bef65bb21ebb6a64aafad448f7f62dc824a CPU threads: 6; OS: Windows 6.19; UI render: default; Locale: en-US (en_US); Calc: CL Looks like a regression.
(In reply to Kira Tubo from comment #6) > Looks like a regression. @Kira, thank you retesting and reveal the regression. This seems to have begun at the below commit in bibisect repository/OS bibisect-linux-64-6.3. Adding Cc: to Mark Hung ; Could you possibly take a look at this one? Thanks b22e80f550338670dbe9cef9370ca97bbae3bd6d is the first bad commit commit b22e80f550338670dbe9cef9370ca97bbae3bd6d Author: Jenkins Build User <tdf@pollux.tdf> Date: Tue Feb 26 05:07:52 2019 +0100 source 7e18b87566c55b38ca812c28b01ed346d45e94b8 68283: tdf#88969 restart interactive sequence. | https://gerrit.libreoffice.org/c/core/+/68283
You don't even need to have "hide after animation" on in the Effect Options to reproduce this. Using an effect from the "Exit" category triggered by object click is enough. And the opposite problem also exists: if an object uses an Entrance effect, it disappears instead at the end. Generalising the issue: Since b22e80f550338670dbe9cef9370ca97bbae3bd6d, an animation that is triggered by clicking another object goes back to its initial state when the animation is finished. This solved bug 88969 and allows repeating such animations without switching slides, but it only works for users who actually want the object to automatically go back to the start state (or for whom it does not matter because the end state is the same as the initial state, i.e. a "cyclic" animation). I'd call this an implementation error rather than a regression. We should either: - allow repeating the animation without the object always settling to its start state; or - make the fix for bug 88969 optional (but the dialog doesn't need more complexity in my opinion) UX/Design team, what do you think?
*** Bug 151096 has been marked as a duplicate of this bug. ***
*** Bug 151097 has been marked as a duplicate of this bug. ***
*** Bug 159648 has been marked as a duplicate of this bug. ***
MSO 365 has 'after animation' options but disables it in case of exit animations. It also has another option "[ ] Rewind when done playing", which can be used on exit animations too, ending up in what is defined at the (disabled) after animation option. At this point I stop discussing MSO's issues. ;-) From the user POV I expect exit animations to 'Hide After Animation' and entry to 'Show After Animation', automatically but optionally. Unfortunately 'hide after animation' does not make the shape disappear but the options 'Dim with color' or 'Hide with next animation' does => bug.