Description: The timings of the "Blink" animation applied to an element are so wrong that the effect is unusable. Steps to Reproduce: Let's suppose we want to apply a blinking effect to some element in a page (not just to a text). 1. Create a new presentation and create some element like a Rectangle or an Ellipse. 2. Select the element and add the "Emphasis: Blink" effect to it, and set the Duration of the effect to some value like 10 seconds. 3. Start the presentation (F5) and click to start the animation. Actual Results: You'll see that the animation duration is not what you set, but something like the half of it. For example, if you set a duration of 10 seconds, the animation will only last for 5 or 6 seconds. Expected Results: If I set a duration of 10 seconds (and no repetitions) I expect the animation to last 10 seconds. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Another problem (I think is related to the above problem) is that if you want to repeat the blinking animation (well, usually just a single blink is not much useful!) the blinking itself will be very strange, much much faster of what you would expect and not much usable, because the time the element is visible is too little compared to the time it's hidden. For example, if you set a Duration of 1 sec and a Repeat value of 10, you would expect 10 blinkings of 1 second each one (so, the animation should last 10 seconds in total). Instead, what you get are 10 strange blinkings (as I said before, during a single blinking, the time in which the element is visible is too little) in about 5-6 seconds. Bug present on versions: 6.3.6.2 (x64) and 6.4.3.2 (x64). I don't know if it affects earlier versions too.
Today I tried on Ubuntu 18.04 LTS: LibreOffice Version: 6.0.7.3 Build ID: 1:6.0.7-0ubuntu0.18.04.10. In this environment the Repeat value doesn't work at all! Whatever value you use for the Repeat field, nothing changes in the animation...
Please don't put several problems on the same bugtracker. One bug per bugtracker.
(In reply to Julien Nabet from comment #2) > Please don't put several problems on the same bugtracker. > One bug per bugtracker. Sorry, you are right. I think the 2 problems are related but I will file a new bug report for it.
Dear Mauro, 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
Bug confirmed on the latest Libreoffice version I downloaded today. Informations from from Help - About LibreOffice: Version: 7.3.3.2 (x64) / LibreOffice Community Build ID: d1d0ea68f081ee2800a922cac8f79445e4603348 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: it-IT (it_IT); UI: en-GB Calc: threaded
The same thing here, please let the bug in Unconfirmed status, until someone else can confirm it.
(In reply to BogdanB from comment #6) > The same thing here, please let the bug in Unconfirmed status, until someone > else can confirm it. Hi, I confirm the bug is always present. I just tried again today to reproduce the bug with the last Libreoffice release (7.5.5.2 x64) on a Windows 10 machine and the 7.3.7.2 x64 release on an Ubuntu 22.04.3LTS machine. I see that this bug has been open since 2020 and so far no one has taken an interest in it (probably because, in the Libreoffice suite, Impress is used much less compared to Writer or Calc), but being that it's very easy to reproduce, can you try yourself and change again the status bug? Thanks. P.S.: there is an Impress version where the "blink" effect works as expected: is the OpenOffice version 4.1.13. I know that is not Libreoffice, but the codebase should be about the same, right? So maybe some developer could check what is gone wrong in that part of code...
Repro Arch Linux 64-bit, X11 Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 60(Build:3) CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US 7.6.0-2 Calc: threaded