When running a formula that applies to an array of cells, pressing Ctrl+Shift+Enter doesn't shift to array mode (which is visible because the formula is enclosed in {} brackets) I tested this under LibreOffice 3.3.3 OOO330m19 (Build:301) tag libreoffice-3.3.3.1 LibO-dev 3.4.0 OOO340m1 (Build:1) and OOo 3.4 Beta (I just noticed you can't copy the version from the About box in Ooo...) with the same results.
Can you please give an example? I tried it as the help says: Select a range of 3 x 3 cells on another part of the spreadsheet, enter the formula =10*A1:C3 and confirm this entry using the key combination Ctrl+Shift+Enter. The result is a 3 x 3 array in which the individual values in the cell range (A1:C3) are multiplied by a factor of 10. And it worked.
(In reply to comment #1) > Can you please give an example? I tried it as the help says: > > Select a range of 3 x 3 cells on another part of the spreadsheet, enter the > formula =10*A1:C3 and confirm this entry using the key combination > Ctrl+Shift+Enter. The result is a 3 x 3 array in which the individual values in > the cell range (A1:C3) are multiplied by a factor of 10. > > And it worked. I think there is some confusion/misunderstanding. What I believe pedlino is referring to is the behaviour that when a formula has *aleady* been entered with the ENTER key, selecting the formula again and then attempting to enter it as an array formula with CTRL+SHIFT+ENTER does not change it to a formula array. I believe this is in response to: http://nabble.documentfoundation.org/Calc-Has-anyone-tested-the-backward-compatibility-of-LibreOffice-3-4-tp3022764p3033637.html
Thanks, Stephan. That is exactly the problem. This is the contents of the workaround found by user "Jack" (just in case the linked post disappears or is moved) "array formulas in LibO/OOo are a little tricky (little more so than in Excel). If you've entered the formula correctly and pressed ENTER (instead of CTRL+SHIFT+ENTER), then obviously it does not work. If you then select the cell/formula again and press CTRL+SHIFT+ENTER, then it *still* won't work, because it doesn't register that you've changed the formula (thus won't take the CTRL+SHIFT+ENTER). You'll need to physically change the formula again and then press CTRL+SHIFT+ENTER (I usually type and erase a space)." It shouldn't be required to use tricks to use this function ;)
The same on Linux (Suse 11.3)
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
needinfo keyword redundant by needinfo status.
Still occurs under 3.5.0 Beta2. Changed to New
Still occurs under 3.6.2.2
** 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.0.3 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) Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-02-19
The bug still occurs in version Version: 4.4.1.1 Build ID: b5ac74bf8683a92078a2bc8aff97d4b436af63cb Locale: pt_PT running under Windows XP Pro x86 SP3
** 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.0.5 or 5.1.2 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: 2016-04-16
No, it is still not fixed Tested with Version: 5.1.2.2 Build ID: d3bf12ecb743fc0d20e0be0c58ca359301eb705f CPU Threads: 4; OS Version: Windows 6.2; UI Render: GL; Locale: pt-PT (pt_PT)
** 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.2.7 or 5.3.3 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-20170522
Bug is still present in version 5.3.3.2 x64, tested under Windows 7 Pro x64 SP. The bug already occurred in OOo 3.3 so I changed the earliest affected Version.
** 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 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 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: 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
Tested with LO 5.4.7 under Windows 7 x64 Problem still occurs.
Dear Pedro, 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 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: 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
Still doesn't work Version: 6.1.6.3 Build ID: 5896ab1714085361c45cf540f76f60673dd96a72 CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk2; Locale: pt-PT (pt_PT.UTF-8); Calc: group threaded or Versão: 6.1.6.3 (x64) ID da versão: 5896ab1714085361c45cf540f76f60673dd96a72 Processos do CPU: 8; SO: Windows 10.0; Gestão da interface: GL; Configuração regional: pt-PT (pt_PT); Calc: CL
The problem still persists. Ubuntu 18.10 LibreOffice Version: 6.3.0.4 Build ID: libreoffice-6.3.0.4-snap1
Libreoffice 6.4.2, year 2020 and this issue is still happening. The workaround described in Comment 3 below still works. In order for ctrl-shift-enter to switch to Array Mode a formula that was manually modified/edited and then entered by pressing just Enter, you need to edit the said formula again, and then "Change it again" by adding a trailing space and removing it, and then press ctrl-shift-enter. This is a bizarre behavior. After pressing F2 on a formula, pressing ctrl-shift-enter to exit editing mode should switch it to Array Mode regardless of whether other changes were made.
Dear Pedro, 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
I understand that in order to fix this technically correct a lot has to change [1] which will take at least "a while". But because this can be a really annoying and useless warning that keeps coming back and disrupts the user experience, I also want to suggest to implement an option like "Don't show this warning again" in the meantime. [1] https://backlinkhub.in/ ps. I have seen bugs that mention this issue, but they either focus on startup or on first use.
*** Bug 158895 has been marked as a duplicate of this bug. ***
*** Bug 162505 has been marked as a duplicate of this bug. ***
Adding content of comment https://bugs.documentfoundation.org/show_bug.cgi?id=158895#c3 so it doesn't get lost: A formula expression not being compiled anew if not modified is on purpose as it usually is unnecessary and only forces recalculation, also of all dependencies. However, if it previously was not an array formula but now is closed with Shift+Ctrl+Enter instead of Enter that should be differentiated and the expression be compiled as array formula. Note that the opposite, formula was array but now is closed with plain Enter, should _not_ be recompiled to not destroy the array mode context. I don't recall why a case such as {=SUM(IFERROR(B6:B125,""))} entered (that creates a text cell) and being edited removes the {} and treats content as normal formula. Probably there was a feature request to do so..