Bug 130570 - Make auto-increment on copied numbers configurable
Summary: Make auto-increment on copied numbers configurable
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.0.3 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: difficultyMedium, easyHack, skillCpp
Depends on:
Blocks: AutoFill
  Show dependency treegraph
 
Reported: 2020-02-10 19:04 UTC by Burg
Modified: 2023-10-07 03:18 UTC (History)
2 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 Burg 2020-02-10 19:04:48 UTC
Example: When a cell filled with the number 200 is dragged on the edge to cells below in the column, these are filled with increments 201, 202 etc. 
This also happens when Tools > Autoinput is unchecked. 

Expected behaviour:
The value 200 should appear in all the cells of the selection.
Comment 1 Xavier Van Wijmeersch 2020-02-11 06:49:43 UTC
You can fill two cells, A1 and A2 with exp 200 select them and then drag them down and you will have in all cells the value 200

You can also ctrl+c select all cells you need and then ctrl+v

Yes i can reproduce but still i think its the way drag and drop works

Best regards
Comment 2 Burg 2020-02-11 12:30:57 UTC
Thanks for the hint.
IMHO, software should never change a value I entered when I did not instruct it to do so. 
Not being able to turn this 'feature' off - is clearly a bug.
Comment 3 Durgapriyanka 2020-02-11 17:17:44 UTC
Thank you for reporting the bug. I can confirm the bug present in

Version: 6.4.0.0.alpha1+ (x86)
Build ID: ec7374ff84c71edfbb30d6e4dc5b486b6df7107f
CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-11-10_21:37:30
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded
	

and in

LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4
Comment 4 Ming Hua 2020-02-11 18:42:00 UTC
I don't think this has anything to do with autoinput.  Autoinput is about suggesting words/entries from the same column when you start typing the first few characters in a cell, not about dragging and filling cells.

This "incrementing numbers" behavior for draging and filling has always been like this in LibreOffice Calc, and I believe always been like this in MS Excel as well.  I doubt changing it is a good idea, no matter it's intuitive or not.

To fill the cells with the same numbers, you can start with two cells with the same numbers as comment 1 suggested, or hold Ctrl key when dragging.

IMHO this is either NOTABUG or WONTFIX.
Comment 5 Burg 2020-02-12 10:46:59 UTC
Ming Hua, ok, so then the title may be changed, the issue remains.
If it was always like this, it was ALWAYSABUG ;-)

In MS Excel, this has to be explicitly defined as a 'series':
https://superuser.com/questions/841439/excel-auto-fill-a-column-with-increment

Maybe for a reason.
Comment 6 QA Administrators 2022-02-12 03:37:20 UTC Comment hidden (obsolete)
Comment 7 Burg 2022-02-12 14:33:16 UTC
Checked again with latest 7.3.0.3 - and the behaviour is unchanged. 

Ming Hua might be right that the developers do not consider this a bug but a feature, and instead of marking it "WONTFIX" decided to ignore it. 

For people new to spreadsheets this might be considered a feature, in order to start quickly with a new sheet. 
But on more complex sheets it can introduce some misunderstanding, because text and formulas are copied 1:1 but number data is silently incremented, not obvious at first sight. 

So maybe we change this bug to a feature request?:
"Make auto-increment on copied numbers configurable"
Comment 8 Mike Kaganski 2023-10-06 07:53:33 UTC
Indeed, the default (i.e., without Ctrl pressed) behavior in e.g. Excel 2016, is to copy the single selected cell, not to auto-increment it.

This is different to the default behavior (without Ctrl pressed) in the same Excel, when two or more cells are selected: then by default, it tries to analyze and continue.

An (advanced?) configuration might be reasonable.

A code pointer: one should check how nScFillModeMouseModifier (sc/inc/global.hxx) is set and used. The code of interest is in sc/source/core/data/table4.cxx; one might need to make the difference between the case when start and end row/columns is the same, vs. when it's different.