Bug #74212 ctrl-Page Up tab selection behavior inconsistent
Submitted: 3 Oct 2014 14:37 Modified: 26 Nov 2014 15:48
Reporter: Joshua Migdal Email Updates:
Status: Verified Impact on me:
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.2.3 OS:Windows (7 64 bit)
Assigned to: CPU Architecture:Any
Tags: query, tabs, UI

[3 Oct 2014 14:37] Joshua Migdal
Tab switching between queries up the top is inconsistent depending on cursor focus

How to repeat:
Have several query tabs open up the top
Run a query in one of them
Put cursor in the results panel to move around

Hit ctrl-page up to move to left query tab. INSTEAD, The execution plan page opens up.

Hit ctrl-page up again, and the query tab moves to the left.

Suggested fix:
Have ctrl-page up/down ALWAYS control query tabs regardless of cursor focus.
[6 Oct 2014 18:10] MySQL Verification Team
Which exactly version are you using 6.2.X?. Thanks.
[7 Oct 2014 13:10] Joshua Migdal build 2280 (64 bits)
[11 Oct 2014 19:38] MySQL Verification Team
Please provide screenshots showing the issue. Thanks.
[14 Oct 2014 13:24] Joshua Migdal
Run query, focus cursor on results grid

Attachment: 1.png (image/png, text), 62.58 KiB.

[14 Oct 2014 13:25] Joshua Migdal
hit ctrl-page up: execution plan shows

Attachment: 2.png (image/png, text), 38.31 KiB.

[14 Oct 2014 13:25] Joshua Migdal
hit ctrl-page up 2 more times, tab switches to the left as expected

Attachment: 3.png (image/png, text), 44.49 KiB.

[14 Oct 2014 13:27] Joshua Migdal
Once the execution plan displays, you actually have to hit ctrl-page up TWICE to get it to move to the left query tab. The first ctrl-page up does nothing.
[14 Oct 2014 17:07] MySQL Verification Team
Thank you for the feedback.
[26 Nov 2014 15:48] Joshua Migdal
Has there been any progress on this? I understand it is not as critical as a crashing bug, but ergonomics is an important aspect of being able to use a product effectively and I find this one in particular hampers my ability to quickly navigate between searches, for comparison and cross-reference style investigations. I'm sure others have similar workflows that would benefit from a fix for this as well (I hope so anyway!)

Thanks kindly.