Bug #74552 Copy results via hot key (Command+C) doesn't always work (inconsistent behavior)
Submitted: 24 Oct 2014 15:27 Modified: 14 Feb 2017 21:19
Reporter: Mike Reid Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:6.3.9 OS:MacOS (10.12 Sierra)
Assigned to: CPU Architecture:Any
Tags: command c, copy, editor, hot key, paste

[24 Oct 2014 15:27] Mike Reid
Description:
When attempting to copy SQL Results using the shortcut keys (Command+C), the copy behavior is not reliable and does not work as expected.

It seems it will work the first time the results panel is focused, but if you leave the application (for example, open up your browser) and then come back to Workbench, the copy command fails to work again until you focus outside the results panel (e.g. clicking in the editor) and then focusing back to results panel.

How to repeat:
1. Open up Workbench and connect to a database

2. Enter some SQL in the editor and execute:

e.g.

USE mysql;
SHOW TABLES;

3. Click on one of the cells (or rows) and copy using the hot key "Command + C"

4. Open up an alternate application on the computer (TextEdit, web browser, etc)

5. Now, switch back to MySQL Workbench.

6. Select a different cell (or row) in the results panel and attempt to copy using the hot key "Command + C"

7. Listen as the error sound indicates the inability to copy. If you attempt to paste from your clipboard, it will contain the value from the first attempt.

Suggested fix:
Attempt to allow copying under ANY circumstance, specifically in this case when leaving and re-entering workbench where results panel was previously focused.
[24 Oct 2014 23:33] MySQL Verification Team
Thank you for the bug report.
[19 Jan 2015 15:45] Mike Reid
Bumped the impacted version up.
[23 Jan 2015 5:06] John Doe
Same exact case for same OS and Version. Cmd+C and then I need to click in the editor pane before I can Cmd+C again.
[14 Feb 2017 21:19] Mike Reid
Bumping impacted version (still affects latest 6.3.9)