Description: I had to UNINSTALL 6.4.5 and download and install 6.3.6 to get back the keyboard arrow movement around cells within LibreOffice Calc. 6.4.5 DID NOT have a choice for using the arrow keys to move up or down to get around in Calc, making it extremely cumbersome to navigate a spreadsheet. The only choice provided was to use the ENTER key to move DOWN to the next cell below. Using the mouse is NOT as efficient as the arrow keys. Arrow keys are faster and more secure, preventing shaky hands navigating to and modifying incorrect/unwanted cells/areas. 6.3.6 has this/these arrow movement functions already enabled. 6.4.5 needs to be updated/corrected to return this/these functions to keep Calc efficiencies high. Steps to Reproduce: 1.Press any arrow key to move from cell to cell. 2. 3. Actual Results: ONLY vertical movement of the ENTIRE spreadsheet occured. NO LATERAL movement occured. Expected Results: Pressing any ARROW key should move from the CURRENT cell to the next (and successive) cell(s) (up - down - right - left) for each key press or MULTIPLES if that arrow key is HELD PRESSED. Reproducible: Always User Profile Reset: No Additional Info: None
Had you pressed ScrollLock keyboard button inadvertently?
(In reply to Mike Kaganski from comment #1) > Had you pressed ScrollLock keyboard button inadvertently? Negative. Once I uninstalled 6.4.5 then installed 6.3.6, with NO keyboard changes, the arrow keys worked as they should so it is a bug, or at least an omission in 6.4.5.
(In reply to Old Heart from comment #2) Yet I would still ask you to test if that was the case. The key state could be e.g. reset on reboot; even if you didn't reboot, testing wouldn't hurt, and would just make the answer definite. Please try installing the program, and test how does it react to Scroll Lock status (Scroll Lock is expected to change the program to behave the way you describe: tdf#46200).
(In reply to Mike Kaganski from comment #3) > (In reply to Old Heart from comment #2) > > Yet I would still ask you to test if that was the case. The key state could > be e.g. reset on reboot; even if you didn't reboot, testing wouldn't hurt, > and would just make the answer definite. Please try installing the program, > and test how does it react to Scroll Lock status (Scroll Lock is expected to > change the program to behave the way you describe: tdf#46200). Tested and proven, screoll lock was NOT pressed during EITHER version installs. Proven the problem ONLY exists in version(s) AFTER 6.3.6. I ask you to check in the TOOLS Options to describe to me where ANY Keyboard actions are enabled or even listed OTHER THAN pressing the ENTER key to move to the cell just BELOW the current cell when the enter key is pressed. There are none. I went there before filing this bug report. I followed EVERY described step to locate the cause of the problem in 6.4.5 but NO solution was effected. But upon uninstalling 6.4.5, restarting the computer and installing 6.3.6 then starting Calc I was able to IMMEDIATELY navigate around any spreadsheet including the one I use for my monthly finances and bills with the arrow keys. This indicates and proves the bug/problem and that 6.4.5 needs to be reviewed and fixed. Thank you for trying but I have my solution, stickling with a version that works for me. And I will stick with this version unless or until I am informed newer versions have and maintain this function in Calc. Now, it is 0148 my time so I'm logging out and going to bed and I will remove my account since I'd only hoped to help others that may encounter this problem, not debate nor trudge through details I don't understand anyhow. Thanks and goodnight and goodbye. Old Heart
Works fine for me: Versión: 6.4.5.2 (x64) Id. de compilación: a726b36747cf2001e06b58ad5db1aa3a9a1872d6 Subprocs. CPU: 4; SO: Windows 10.0 Build 19608; Repres. IU: predet.; VCL: win; Configuración regional: es-ES (es_ES); Idioma de IU: es-ES Calc: Have you tested with a clean profile?, Menu/Help/Restart in Safe Mode
I can confirm that this WORKSFORME in the following builds: Version: 6.4.6.2 (x64) Build ID: 0ce51a4fd21bff07a5c061082cc82c5ed232f115 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win; Locale: en-AU (en_US); UI-Language: en-GB Calc: CL and Version: 7.1.0.0.alpha0+ (x64) Build ID: e69fafe1873e4afbe739f21f7a82a069cf7eb5b2 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: en-AU (en_US); UI: en-GB Calc: CL
(In reply to m.a.riosv from comment #5) > Have you tested with a clean profile?, Menu/Help/Restart in Safe Mode Old Heart: still the same with 7.1? And with Safe mode? Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists in Safe mode. Change to RESOLVED WORKSFORME, if the problem went away.
Dear Old Heart, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Old Heart, 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-FollowUp