Bug #43787 keyboard arrow up/down does not work properly
Submitted: 22 Mar 2009 10:22 Modified: 29 Jan 2018 10:46
Reporter: Peter Laursen (Basic Quality Contributor) Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.1.9 OS:Windows
Assigned to: CPU Architecture:Any
Tags: qc

[22 Mar 2009 10:22] Peter Laursen
Description:
I find several places (all?) in the GRID editor where keyboard arrow-down does not prepare next row for input.

How to repeat:
I will upload an image

Suggested fix:
Any decent GRID based data editor accepts keyboard arrow events.  It is an annoyance to shift hands' position between mouse and keyboard.
[22 Mar 2009 10:23] Peter Laursen
here I need to click twice to enter next column name - arrow-down should do!

Attachment: ddledit.jpg (image/jpeg, text), 14.90 KiB.

[22 Mar 2009 10:39] Peter Laursen
changing to S2 category.  It is almost unusable like this!
[22 Mar 2009 14:54] MySQL Verification Team
Thank you for the bug report.
[27 May 2009 20:43] Johannes Taxacher
hi peter,

do you really think its almost unusable like this? when in the editor grid, pressing F2 (which is the default key for going into edit-mode in windows iirc) will let you enter data. jumping to the datatype dropdown can be accomplished by using the tab key. once the change has been committed using the enter key you can use the down key to highlight the next (empty) row ... 
Entering the edit mode using the mouse is a tricky - we still have to improve this. just asking if i'm missing sth here.
[27 May 2009 20:47] Peter Laursen
Try some other GUI tool using a GRID interface (a client for any database server or a spreadsheet).  None I can think of is so akward for users! Maybe I could learn it but I have no intention to use a tool where I need to do this-and-that-and-dut :-)
[16 Oct 2009 11:54] Susanne Ebrecht
Peter,

honestly, Workbench is a GUI tool. And usually users who use GUI tools are using the mouse too.

All works fine by using the mouse.

So I am not able to see this as serious bug.

In my eyes it is a feature request. A feature request which we should implement soon but anyway a feature request.
[19 Oct 2009 7:46] Peter Laursen
Classification is your decision of course.
[29 Jan 2018 10:46] Mike Lischke
Posted by developer:
 
The current behavior is imposed by the system control we use (the Microsoft data grid). There are no plans to replace that in the foreseeable future. If we do, we will consider a different keyboard handling for sure.