Bug 104185 - Better Autoinput for functions (or different default than ENTER)
Summary: Better Autoinput for functions (or different default than ENTER)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.1.5.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsDevEval
Depends on:
Blocks: Calc-Function
  Show dependency treegraph
 
Reported: 2016-11-26 13:46 UTC by Mieszko
Modified: 2020-03-09 13:27 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 Mieszko 2016-11-26 13:46:40 UTC
Description:
I think ENTER it shouldn't be default for Autoinput. It is frustrating when you want '=O' (what is e.g. defined as custom name of my cell), hit ENTER and sth else is given. More resonable is SHIFT + ENTER, or SHIFT-TAB, or CTRL + SPACE (last like in many programming IDE). Or even Tab is better (although user could want go to next cell) - just type TAB once to complete and SHIFT-TAB to back, or many TABs for scroll through list of possibilities.

I'm don't know many things. It's just an opinion of a one end user.

Steps to Reproduce:
1. press SHIFT-CTRL-F2
2. type =P
3. hit ENTER

Actual Results:  
=PEARSON() applied and go one cell down.

Expected Results:
=P applied [and go one cell down].
[] - or not


Reproducible: Always

User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
Builds ID: LibreOffice 5.1.5.2


User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.100 Safari/537.36
Comment 1 Buovjaga 2016-11-29 19:35:38 UTC
So what do we do after we change the default and millions of angry users attack?
Comment 2 Mieszko 2016-11-30 11:21:01 UTC
So just add possibility to change it in settings. You know better what is good as default, I've only mention what would be better for me (and I consider it as more logical), just as a feedback.

BTW* this would not be so big change as when you break compatibility in macros for ver.4 vs ver.5. People can learn minor changes in gui/behavior, but cannot keep running their scripts.
*Its 'btw'. I doesn't mean I want force my point of view.
Comment 3 Mieszko 2016-11-30 11:47:12 UTC
**Solution**
for people who don't want this feature

-> uncheck tools/autoinput
but this doesn't switch it off at all. If you type more letters and than delete them by backspace, autoinput still works.

If don't want switch autoinput off or be sure that this will never happen accidentialy, teach your muscle memory to use TAB, ENTER instead of ENTER.
Comment 4 Heiko Tietze 2016-12-05 09:52:07 UTC
Typically the dropdown for autocomplete shows up and after selecting one the items it is inserted with enter. Having another option like (o) Enter, () Shift+Enter, () Ctrl+Enter sounds like an overkill.

However, we could change the autocomplete behavior. As reported by Mieszko the functions is not shown when text is added and AutoInput (bad camel case) is disabled but pops up on backspace. And when this bug is solved we could introduce a manual autocomplete like the user enters =p and presses <F2> (use a good shortcut here) the function list is shown. But the selection of an entry would be done per Enter.

unconfirmed -> new
enhancement -> normal since autocomplete is buggy for backspace. 
-needsUXEval +needsDevEval
Comment 5 QA Administrators 2018-07-23 02:32:12 UTC Comment hidden (obsolete)
Comment 6 Mieszko 2018-07-23 08:26:55 UTC
Hi,

The looks of auto-input has been changed but disabling tools->auto-input still doesn't work on backspace press.

Version: 6.0.4.1
Build ID: 00m0(Build:1)
CPU threads: 4; OS: Linux 4.16; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: group
Comment 7 QA Administrators 2019-07-30 03:16:42 UTC Comment hidden (obsolete)
Comment 8 Xisco Faulí 2020-03-09 13:27:47 UTC
Please add keyword 'needsUXEval' and CC 'libreoffice-ux-advise@lists.freedesktop.org' if input from UX is needed.