MySQL Bugs: #2412: inconsistency between behavior of tab and enter key in query window

Bug #2412	inconsistency between behavior of tab and enter key in query window
Submitted:	15 Jan 2004 13:00	Modified:	1 Jun 2004 0:36
Reporter:	Justin Watt	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQLCC	Severity:	S3 (Non-critical)
Version:	0.9.4-beta	OS:	Windows (Windows 2000)
Assigned to:	Bugs System	CPU Architecture:	Any

Description:
When you're editing a field (after having double clicked it) and you press tab, it brings you to the next field to the right and positions the cursor at the end of the text in that field.

When you're editing a field and you press enter (or return), it brings you to the next field below, but does not position the cursor at the end of the text in that field, rather it only sets the focus on that field. Oo if a user starts typing, they may mistakenly overwrite any existing text in that field.

How to repeat:
1)double-click on field to start editing it
2)press tab
(mysqlcc brings you to the next field to the right and positions the cursor at the end of the existing text in that field)
3)press enter
(mysqlcc brings you to the next field below and sets the focus to the field, but does not position the cursor in that field

Suggested fix:
make the enter key behavior match the tab key behavior, so that when you're in edit more, you stay in edit mode.

bug 2410 advises that when in focus mode (having single clicked a field) you should stay in focus mode when using the tab key, similar to the behavior of the enter key.

Verified; thank you!

Hi!

MySQLCC has been discontinued and will not be developed nor maintained anymore with the exception of Critical bugs.

In the near future we will release the substitute of MySQLCC called MySQL Query Browser.