Description: Attached sample - NoBlink.ods. Both cells have been established with blinking text but the text will only blink if their names are deleted. Re-establishing their names expunges the blink Steps to Reproduce: With the attached file Satisfy yourself that all parameters are functionally correct for the inserted shapes Right click either object select name Delete the name Observe the object now blinks as commanded Undo or give the object a new name Observe the object no longer blinks If, it's not a bug then perhaps the help should be updated to inform users of the restrictions 2. 3. Actual Results: Non-blinking text within the shape Expected Results: Blinking text within the shape Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Version: 7.2.4.1 (x64) / LibreOffice Community Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: sv-SE (en_GB); UI: en-GB Calc: threaded
Created attachment 176895 [details] Supporting .ods
It also will not blink for a shape inserted into a writer document but I have no idea how to find the "name" field as it doesn't appear when right clicking the object
I'm a little confused. Reading the report Mike appended leaves me unsure whether the blinking shouldn't really exist in LO or just not in Writer.
Not sure if this is the right forum for making a Related suggestion. If the blink functionality is to be retained in CALC, would it be worth considering incorporating it into the style and conditional formatting protocols? I would certainly use it as a means of drawing attention to pre-defined circumstances affecting individual (or ranges of) cells and I imagine other users, if aware of the facility, would also find it appealing.
This seems to have begun at the below commit. Adding Cc: to Armin Le Grand; Could you possibly take a look at this one? Thanks e9c172564ab3d3acc38dc64da9247dd4bfc647a0 is the first bad commit commit e9c172564ab3d3acc38dc64da9247dd4bfc647a0 Author: Matthew Francis <mjay.francis@gmail.com> Date: Fri Sep 18 10:43:53 2015 +0800 source-hash-eceecd4a3806f64c2e8fb0a3bcdcc43e1384779f commit eceecd4a3806f64c2e8fb0a3bcdcc43e1384779f Author: Armin Le Grand <alg@apache.org> AuthorDate: Fri May 4 14:16:22 2012 +0000 Commit: Caolán McNamara <caolanm@redhat.com> CommitDate: Wed Mar 13 11:22:20 2013 +0000 Related: #i119125# corrected gradient rendering and added stuff to add Title and Description to primitives for later usage
It does not only happen for "Blink" but for the other text-animations (Text_Marquee) too. It was OK in OOo3.2, it fails in AOO 4.1.6.
This commit was developed for another code base, and not merged by me. For complex changes like this, side-effects are to be expected; sadly I dont't have the cycles to deal with all the fallout. Un-Ccing myself for the while.
Dear Colin, 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
(In reply to QA Administrators from comment #8) > Dear Colin, > > If you have time, please do the following: > Due to outstanding critical bugs I am Unable to use anything later than Version: 7.5.9.2 (x86) / LibreOffice Community Build ID: cdeefe45c17511d326101eed8008ac4092f278a9 CPU threads: 12; OS: Windows 10.0 Build 26100; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded Perhaps somebody else could test. Failing that, it's no longer important for me as my workaround - don't bother to use the function - works admirably