Bug 38014 - Pressing Ctrl+Shift+Enter doesn't switch to array mode
Summary: Pressing Ctrl+Shift+Enter doesn't switch to array mode
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Shortcuts-Accelerators
  Show dependency treegraph
 
Reported: 2011-06-06 16:09 UTC by Pedro
Modified: 2024-01-24 11:38 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pedro 2011-06-06 16:09:38 UTC
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.
Comment 1 Andras Timar 2011-06-06 23:52:54 UTC
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.
Comment 2 Stephan Zietsman 2011-06-07 02:05:27 UTC
(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
Comment 3 Pedro 2011-06-07 06:18:01 UTC
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 ;)
Comment 4 wope 2011-06-18 11:59:27 UTC
The same on Linux (Suse 11.3)
Comment 5 Björn Michaelsen 2011-12-23 12:29:34 UTC Comment hidden (obsolete)
Comment 6 Björn Michaelsen 2011-12-23 17:02:36 UTC
needinfo keyword redundant by needinfo status.
Comment 7 Pedro 2012-01-03 16:49:01 UTC
Still occurs under 3.5.0 Beta2. Changed to New
Comment 8 John Russell 2013-03-30 09:38:15 UTC
Still occurs under 3.6.2.2
Comment 9 QA Administrators 2015-02-19 15:49:44 UTC Comment hidden (obsolete)
Comment 10 Pedro 2015-02-21 10:47:59 UTC
The bug still occurs in version

Version: 4.4.1.1
Build ID: b5ac74bf8683a92078a2bc8aff97d4b436af63cb
Locale: pt_PT

running under Windows XP Pro x86 SP3
Comment 11 tommy27 2016-04-16 07:29:04 UTC Comment hidden (obsolete)
Comment 12 Pedro 2016-04-20 23:13:50 UTC
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)
Comment 13 QA Administrators 2017-05-22 13:27:32 UTC Comment hidden (obsolete)
Comment 14 Pedro 2017-05-22 14:25:30 UTC
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.
Comment 15 QA Administrators 2018-06-04 02:33:54 UTC Comment hidden (obsolete)
Comment 16 Pedro 2018-06-04 09:05:35 UTC
Tested with LO 5.4.7 under Windows 7 x64
Problem still occurs.
Comment 17 QA Administrators 2019-06-05 02:54:29 UTC Comment hidden (obsolete)
Comment 18 Pedro 2019-06-05 08:58:08 UTC
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
Comment 19 John Russell 2019-08-19 08:23:57 UTC
The problem still persists. 

Ubuntu 18.10
LibreOffice
Version: 6.3.0.4
Build ID: libreoffice-6.3.0.4-snap1
Comment 20 Ariel 2020-05-17 17:28:11 UTC
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.
Comment 21 QA Administrators 2022-05-18 03:36:08 UTC Comment hidden (obsolete)
Comment 22 FrostNeil 2024-01-24 11:38:39 UTC
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.