Created attachment 144014 [details] File to test UI for animation The text in the attached file has an animation "Appear" with setting "Word by word". Open the advanced animation settings. You see a label "delay between characters". The shown value is "34.567%" for me with German local with dot as thousand separator. But actually * the value is not a percent [percent of what should it be?] * the value is not "between characters" but "between words" * the value is written to file as PT00H00M00.34567S. That means it is in fact 0.34567 seconds. Expected behavior: The field acts as a metric field for decimal in unit 'seconds'. The unit of the field is mentioned. The label adapts to the chosen affect. If you newly create such animation, the default value is "10%". That is unsuitable, because it will result in a duration of 0.0001 seconds. The complete animation will play nearly at once. The user will think, that the animation does not work and he gets no information about the needed magnitude.
Created attachment 144017 [details] Test FlyIn animation with Word-by-Word I have now tested animation Typ "Fly In". This animation type has a field "Duration". And in this case a value of "10%" for "delay between characters" makes more sense. It refers to the field "Duration". So a setting of "Duration"=3sec and "Delay between characters"=10% results in anim:iterate-interval="PT00H00M00.3S" in the file. The actual duration of the effect is then "iterate-interval"*"number of parts". In this case, the user does not know the reference of the percent value. And the actual duration of the effect is different from "Duration". So still a bad UI.
As shown here https://opengrok.libreoffice.org/xref/core/sd/source/ui/animations/CustomAnimationPane.cxx#1159 The number in percentage of duration if duration is defined, and is in 10 milliseconds if duration is not defined. And here https://opengrok.libreoffice.org/xref/core/sd/source/ui/animations/CustomAnimationPane.cxx#1291 not sure what will happen when duration is not defined. So there is some problem when display the iterate interval.
Heiko, I think need some UX love for this. What do you think?
(In reply to Roman Kuznetsov from comment #3) > Heiko, I think need some UX love for this. What do you think? Ordinary bug, IMHO. As Regina expects "The field acts as a metric field for decimal in unit 'seconds'" (maybe milliseconds). "All at once" disables the field and letter or word take the value. Default is today 10%, which should be 0.25s per word and 0.1s per letter, or the like. Btw, +/- don't work for me and I cannot enter a value. Version: 6.1.4.2 Build ID: 6.1.4-1 CPU threads: 8; OS: Linux 4.20; UI render: default; VCL: gtk3; Locale: de-DE (en_US.UTF-8); Calc: group threaded
Dear Regina Henschel, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The problems still exist as described in Version: 7.2.0.0.alpha0+ (x64) Build ID: 90668f3473f4e52cec823ad39c6fcb44ba7c089b CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: default; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL
Dear Regina Henschel, 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
Hello, I also have problems with this function on my Windows 11. I have to set the "appear" option to "letter by letter" at 10000% to get anything remotely correct. However, the speed accelerates between each letter and doesn't give a clean result. So I guess the bug still hasn't been solved. Good day !