Description: Help for 7.5 says: Option key '''Cells are moved and shift the cells in the target area to the right or to the bottom. Source cells are emptied, except if you move within the same rows on the same sheet. If you move within the same rows on the same sheet, the cells in the target area shift to the right, and then the whole row shifts to fill the source area.''' But this is not what happens. the cells are copied into a new column, and the original cells remain. Also, what I really want is ot be able to move columns AND THE REFERENCES TO THEM, so that I can re-order the columns. That does not appear to be what this does. Steps to Reproduce: 1. select cells. 2. click option and drag to new cell, different row 3. new cells/column should appear Actual Results: new column created with copy of cells. Expected Results: cells are MOVED Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.7.2 / LibreOffice Community Build ID: 723314e595e8007d3cf785c16538505a1c878ca5 CPU threads: 16; OS: Mac OS X 12.6.7; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
In Windows, cells are moved and remaining cells are shifted when holding Alt (Option in Mac?). To create a new column with a copy I must hold Ctrl+Alt (Ctrl+Option in Mac?) at the release of the mouse button. Help page referenced: https://help.libreoffice.org/latest/en-US/text/scalc/guide/move_dragdrop.html I can't find the MacOS help variant. Version: 7.4.7.2 (x64) / LibreOffice Community Build ID: 723314e595e8007d3cf785c16538505a1c878ca5 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: es-MX (es_ES); UI: en-US Calc: CL
Hi ksdavidc@gmail.com, Thank you for reporting the bug. I can confirm that the bug is present in the latest version. Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 12; OS: Mac OS X 13.5; UI render: Skia/Metal; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
*** This bug has been marked as a duplicate of bug 136389 ***