Hi. This is about effects in presentations. For several of then (e.g. Fly In and Fly Out) a Direction can be specified. This reads always: "From ..." (e.g. From bottom, From left, etc.). Obviously this is only correct for e.g. Fly In but not for Fly Out, where it should read: "To ..." (e.g. To bottom, To left, etc.) Cheers, Chris
I need more information than this. I don't even see Fly Out in 3.6.1.2, also where do you set a direction? Please provide exact steps to reproduce as well as your operating system and LibO version. Marking as NEEDINFO, once you provide steps and info please mark as UNCONFIRMED. Many thanks
Seems like wrong writing that cause misinterpretation. > This reads always: > "From ..." (e.g. From bottom, From left, etc.). Select an object/text > Custom Animation pane > Add > Entrance > Fly In > OK > see that we can select From bottom, From left, etc under 'Direction' > Obviously this is only correct for e.g. Fly In but not for Fly Out, where it > should read: > "To ..." (e.g. To bottom, To left, etc.) Select an object/text > Custom Animation pane > Add > Exit > Fly Out > OK > see that we can select From bottom, From left, etc under 'Direction' -> I agree it should be written: To bottom, To left, etc Don't know it should be categorized as enhancement or bug? LO 4.0.4.1 (Win7 32bit)
CONFIRMED on Ubuntu 12.04.3 with LibreOffice Version: 4.2.0.1 (In reply to comment #2) Repro steps: > Select an object/text First, open a new presentation and create a new rectangle somewhere in the middle of the screen. > Custom Animation pane > Add > Entrance > Fly In > OK * Right-click on rectangle -> Custom Animation -> (Custom Animation pane appears on RHS of screen) * Click "Add" (actually, the text is "+", not "Add" -- that's another bug!) * Select Entrance -> Fly In * Click 'OK' button > > see that we can select From bottom, From left, etc under 'Direction' Yep > > Obviously this is only correct for e.g. Fly In but not for Fly Out, where it > > should read: > > "To ..." (e.g. To bottom, To left, etc.) Confirmed. > Don't know it should be categorized as enhancement or bug? The language needs to be fixed (we're not adding any new functionality), so it's a bug. Status: NEW
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (4.4.1 or later) https://www.libreoffice.org/download/ *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
The issue is still present in 4.4.2.2, Linux.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Still reproducible. Version: 6.2.0.0.alpha1+ Build ID: 0378bfcea51ff0f379d0954aa6740f1829909dc3 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: de-DE (de_DE.UTF-8); Calc: threaded
*** Bug 61710 has been marked as a duplicate of this bug. ***
Created attachment 154406 [details] Bug in Diagonal Squares transition. Confirmed in LO Impress 6.2.0.3. Text of Direction in animation "Diagonal Squares" is "From Left to ..." but really is "To Left to ..." or simply "Left to ..." ¿native english here? Konfirmita en LO Impress 6.2.0.3. Teksto de Direkto en movbildo "Diagonalaj Kvadratoj" estas "From Left to ...", sed vere estas "To Left to ...", aŭ simple "Left to ...". Ĉu iu denaska homo en angla lingvo ĉi tie?
Katarina Behrens committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/398c13f84b1977acf2c63f2159cf0255b3494bdc tdf#48551: change preset subtype of Fly Out and Crawl Out exit animations It will be available in 7.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Katarina Behrens committed a patch related to this issue. It has been pushed to "libreoffice-7-1": https://git.libreoffice.org/core/commit/aa0b23a89dfd12dcd0de8f0ba6d302707a6b628c tdf#48551: change preset subtype of Fly Out and Crawl Out exit animations It will be available in 7.1.4. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
*** Bug 85788 has been marked as a duplicate of this bug. ***