Bug 42814

Summary: Suggestion: Better Usability / Compatibility
Product: [Applications] calligrasheets Reporter: jon
Component: generalAssignee: Laurent Montel <montel>
Status: RESOLVED FIXED    
Severity: wishlist    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:

Description jon 2002-05-19 20:02:40 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kspread
Version:           KDE 3.0.5 CVS/CVSup/Snapshot
Severity:          wishlist
Installed from:    Compiled sources
Compiler:          Not Specified
OS:                Linux
OS/Compiler notes: Not Specified

I would be able to use KSpread instead of Excel in Windows if it only had this one usability feature.  And that is the ability to move to the next cell by clicking on the "Tab" button.  As it stands right now every time you click on the "Tab" key it simply moves around the menu buttons which is very annoying.  Excel does a great job of not only moving to the next cell to the right when you click on the "Tab" key but it also recognizes how you're entering data.  For example if I input something into A1 and click tab it goes to A2 then to A3 and so on --- and then when I click on the "Enter" key instead of simply going down it returns to B1.

These simple functions make Excel and I think could make KSpread incredibly user-friendly.

Other than that I think KSpread and the rest of KOffice is awesome!

(Submitted via bugs.kde.org)
Comment 1 John Dailey 2002-05-22 02:56:27 UTC
The problem with using the tab key while editing the cell contents has now=
=20
been fixed.  The 'carriage return' effect with the enter key has not yet be=
en=20
put in.
Comment 2 Norbert Andres 2003-02-08 18:34:12 UTC
Subject: Re: Suggestion: Better Usability / Compatibility

Thank you for your bug report.
The feature that you requested has been implemented in the latest
development (CVS) version of KDE. The feature request will be closed.

Jumping to the first cell of the next (visible) row is now also implemented.

Regards
NOrbert