MySQL Bugs: #53333: Windows hotkeys reverted / acting strangely

Bug #53333	Windows hotkeys reverted / acting strangely
Submitted:	30 Apr 2010 18:52	Modified:	3 May 2010 20:45
Reporter:	Daniel Katz	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.20	OS:	Windows (7)
Assigned to:		CPU Architecture:	Any
Tags:	execute current statement, execute statement, hotkey, hotkeys

Description:
Previously the change was made for execute current statement to be ctrl-enter and execute all to be ctrl-shift-enter.

I'm noticing in the changes that ctrl-enter is now /behaving/ the same as ctrl-shift-enter.

Also of note is that from the toolbar menu (Database -> ...) the visual cue is that execute current statement is mapped to ctrl-f14.  Do most keyboards even have an f14?  In the US, 104 layout, f1-f12 is the common setup.

However really, ctrl-enter should go back to execute current statement.

How to repeat:
Open 5.2.20 browser, use hotkey ctrl-shift-enter.  It correctly executes all. 
Then use ctrl-enter, notice it ALSO executes all commands in the active window.

Suggested fix:
Revert ctrl-enter to execute current statement rather than ctrl-enter acting the same as ctrl-shift-enter.

Change visual cue to user/actor to reflect change in top menu.

Thank you for the bug report.

This is a duplicate of Bug #53244