Download it now!
Bug 142214 - Improve Calc's auto-complete feature
Summary: Improve Calc's auto-complete feature
Status: ASSIGNED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.7.2 release
Hardware: All All
: medium enhancement
Assignee: Dennis Francis
URL:
Whiteboard: target:7.2.0
Keywords:
: 43742 (view as bug list)
Depends on:
Blocks: AutoCorrect-Complete
  Show dependency treegraph
 
Reported: 2021-05-11 09:07 UTC by Dennis Francis
Modified: 2021-06-09 07:25 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 Dennis Francis 2021-05-11 09:07:58 UTC
Description:
Calc's auto-complete behaviour is different from that of its other popular alternatives and there is some scope for user experience improvement by reducing differences such as:

1. Calc auto-complete should offer suggestions only from the block of nonempty cells above/below the current cell; ie. imagine you have "Hello" in A1. When the user is in A2, they should be getting suggestions when they start typing an "H"; but when the user is in in A4, A5 or A1000, there should be no suggestions at all.

2. It should offer no suggestions until it is completely clear that there are no options any more ie. imagine you have "Hello", "Hero", "Hesitate" in A1, A2, A3. When in A4, and press "H" -> just "H" appears, now on adding an "e" -> still no suggestion, and finally on adding a "s" -> suggestion "Hesitate" (with the "itate" selected) appears. Currently Calc starts showing auto-completion with some chosen word from the list of possible matches, so the user has to pay close attention whether the current completion is correct or not.

Steps to Reproduce:
Currently Calc's behaviour is different from the points (1) and (2) mentioned in the description.

Actual Results:
For point (1) Calc auto completes even in A4 or A5 or A1000
For point (2) Calc auto completes to "Hello" on typing just "H" even though there are other choices.

Expected Results:
Mentioned in the description in points 1 & 2.


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.4.7.2
Build ID: 1:6.4.7-0ubuntu0.20.04.1
CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: gtk3; 
Locale: en-US (en_IN); UI-Language: en-US
Calc: threaded
Comment 1 Commit Notification 2021-05-13 14:24:37 UTC
Dennis Francis committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/f8039c6d645acb015a6c4e45000bbfd1311bfea3

tdf#142214: show autocompletion only if there is...

It will be available in 7.2.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 2 Commit Notification 2021-05-13 14:24:47 UTC
Dennis Francis committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/ca2ec443893731093970914feb750b31ea13e47f

tdf#142214: autocomplete: do not search across empty blocks

It will be available in 7.2.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 3 Commit Notification 2021-05-13 14:25:57 UTC
Dennis Francis committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/06c360d4d27ab0dadfdcd5f9d4f0c87288d3cb75

tdf#142214: unit-tests for new behaviour of auto-complete

It will be available in 7.2.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 4 Commit Notification 2021-05-13 14:26:07 UTC
Dennis Francis committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/ebff4e5181b102e5184277f57fda32fcce60431f

tdf#142214: autoinput: remove search/entry count limits

It will be available in 7.2.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 5 Commit Notification 2021-05-13 14:30:19 UTC
Dennis Francis committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/17d4221c047eac47e26465ddc72d13fb89284f57

tdf#142214: unittest:test autocomplete through numeric block

It will be available in 7.2.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 6 Buovjaga 2021-06-04 06:35:27 UTC
*** Bug 43742 has been marked as a duplicate of this bug. ***
Comment 7 Buovjaga 2021-06-08 05:09:31 UTC
Dennis: there are a couple of reports that requested autocompletion by most used: bug 78545, bug 117344. What do you think about the approach? Should I keep them as closed or open one of them?
Comment 8 Dennis Francis 2021-06-09 07:25:24 UTC
(In reply to Buovjaga from comment #7)
> Dennis: there are a couple of reports that requested autocompletion by most
> used: bug 78545, bug 117344. What do you think about the approach? Should I
> keep them as closed or open one of them?

Keeping one of them open would make sense I think as this bug focus on the conventional behaviour of autocomplete so somewhat different from them.