Bug 108267 - Calc: for some tasks nearly unusable/ error provoking because of word completions
Summary: Calc: for some tasks nearly unusable/ error provoking because of word complet...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.3.3.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-31 14:41 UTC by kohlhz
Modified: 2018-07-31 09:42 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
simplified example (grown naturally) (60.67 KB, application/vnd.oasis.opendocument.spreadsheet)
2017-06-01 09:55 UTC, kohlhz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kohlhz 2017-05-31 14:41:46 UTC
Dependend from the table content, any automatic change may be a major error source. 

For some contents - e.g. a table containing exact data of lens descriptions - it's nearly impossible to use Calc becaue of it's excessive correction behavior.
Given an very correct input, for nearly all new cells I've to correct back one or more times. 
Many cells are having contents with the same beginning. Upper and lower chars can be found at any place, any word begin shouldn't lead to an automatic change.

There should be a way - a simple and lasting preset! - to avoid all the unwanted flood of "extra goodies" - input corrections, word completions, addition of e.g. 1 for the next cell ...
Despite an annoying need to concentrate on automatic "corrections" instead of a concentration to input correct cell data it's nearly impossible to hold one of my calc files without new errors because of automatic "corrections".

This preset to make no automatic change should be indepent from presets for other Office products.

Maybe you are seeing no error in this forcing behavior leading necessarily to crazy wrong table contents - in this case please change this to an amendment

(for some years dependend from Calc file content I used other products because of this Calc behavior. This product isn't provoking wrong content in the actual cell, but wrong contents in neighboring cells because of "extra goodies" ...)
Comment 1 Xisco Faulí 2017-05-31 14:55:32 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 2 kohlhz 2017-06-01 09:55:08 UTC
Created attachment 133780 [details]
simplified example (grown naturally)

In line 346 I've added a new, typical sample entry.
You may manually write this text into line 345, or play with other data.

This example showing just a part of all irritating effects.
The original data are very different, often incomplete or uncertain, and sometimes comments to different entries are necessary.
For such data would be best to have no automatic change of values at all beside of evaluating explicit formulas.

There are other error prone actions due to automatic actions:
E.g.: 
- filling a "-" sign into a cell followed by a tab, should work like working with other data - put in this sign and go to the next cell.
- filling subsequent cells using mouse action shouldn't change the cell content
  (not 100 -> 101 102 103 but 100 -> 100 100 100)
- no automatic input text correction at all

When changing (mainly simplifying) my data I saw indeed some errors in the file, but most wrong contents are not as easy to see like F=136 instead of F=135 (but even 136 could be correct!).
In most cases I had just written a correct, simple and usual text or number like e.g. 4.5 in column S followed by a tab ( or 11|1 into column H)
Such errors are very hard to find, or it's even impossible.

O.k.- the file design is very old and not optimal, I could change it (but e.g. more columns wouldn't make things better)
Comment 3 QA Administrators 2017-12-04 12:45:51 UTC Comment hidden (obsolete)
Comment 4 kohlhz 2017-12-04 17:45:48 UTC
I think, it's an obvious need to have a (simple) possibility to unset every of the "comfort options" which are changing user input. To have such an option would be all I would need.

In the last month I've seen some nasty errors in my data set due to bothersome automatic cell entry completions, which I had to correct by inspecting old data savings of more than a year. I'm hoping I've got all.
Trying to avoid such a painful and time consuming action I'm now therefore using Gnumeric for one of my calc files, knowing that this product is setting up an usage problem Calc isn't having.

For me it's therefore less necessary that you're holding your product at a useful stage.
I'm hoping, that in future concurrent products are mature enough to leave Calc.
Comment 5 QA Administrators 2018-07-03 14:15:49 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2018-07-31 09:42:13 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20180731