https://bugs.documentfoundation.org/show_bug.cgi?id=104185
--- Comment #11 from [email protected] --- In case anyone's interested, I think I've pinpointed the part of the code where function autoinput happens, with stephane's help. In core/sc/source/ui/app/inputhdl.cxx , there's this segment under ScInputHandler::KeyInput : case KEY_RETURN: // New line when in the input line and Shift/Ctrl-Enter is pressed, // or when in a cell and Ctrl-Enter is pressed. if ((pInputWin && bInputLine && bControl != bShift) || (!bInputLine && bControl && !bShift)) { bDoEnter = true; } else if (nModi == 0 && nTipVisible && pFormulaData && miAutoPosFormula != pFormulaData->end()) { PasteFunctionData(); bUsed = true; } else if ( nModi == 0 && nTipVisible && !aManualTip.isEmpty() ) { PasteManualTip(); bUsed = true; } // And a few blocks down... case KEY_TAB: if (bControl && !bAlt) { if (pFormulaData && nTipVisible && miAutoPosFormula != pFormulaData->end()) { // Iterate NextFormulaEntry( bShift ); bUsed = true; } else if (pColumnData && bUseTab) { // Iterate through AutoInput entries NextAutoEntry( bShift ); bUsed = true; } } Move that PasteFunctionData block down to tab's handling and I think that should make it the new function entry key. User setting based would be optimal imo, but I haven't looked into how settings work. Would start from SC_MOD()->GetAppOptions().GetAutoComplete() and try to make a replica of the process. -- You are receiving this mail because: You are the assignee for the bug.
