Search

[SSDT] F6 to move between panes in a query window by Jamie Thomson

Closed
as Fixed Help for as Fixed

9
0
Sign in
to vote
Type: Suggestion
ID: 780990
Opened: 3/8/2013 2:28:22 AM
Access Restriction: Public
0
Workaround(s)
I have *almost* fully made the switch from SSMS to SSDT for all my development needs. The one thing about SSMS that keeps me going back to it is better support for keybaord shortcuts.

One that I us a lot is the F6 key to move between the query, results & messages panes in a query window. Unfortunately this doesn't exist in SSDT, and its enough to send me back to SSMS.
Details (expand)

Product Language

English

Category

Developer Tools (SSDT, BIDS, etc.)

Proposed Solution


Make F6 do the same in a SSDT query window as it does in a SSMS query window.

Primary Benefit

Improved User Interface

Other Benefits


Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Brett Gerhardi GRG on 3/27/2013 at 5:48 AM
Note that this is also showing on the front screen of the connect site as a "Suggestion Implemented" see below.

Really very poor. I thought connect was a great idea until I've found no suggestions ever actually get dealt with


Latest Suggestion Implemented to date: 13,630

[SSDT] F6 to move between panes in a query window

by: Jamie Thomson | on: SQL Server
Posted by Jamie Thomson on 3/13/2013 at 4:00 AM
Hi Gareth
> "This should probably be logged as a feature request"

I quite agree. note that I didn't raise it as a bug, I raised it as a suggestion (aka a feature request).

regards
JT
Posted by Gareth Stephenson on 3/13/2013 at 3:50 AM
Probably because this isn't a "bug", as it isn't causing undesired or unpredictable behaviour.
This should probably be logged as a feature request, as what you're requesting is essentially a new feature to SSDT.
Posted by Jamie Thomson on 3/13/2013 at 2:58 AM
Why is it "closed as fixed" then if it hasn't been fixed?
Posted by Microsoft on 3/12/2013 at 5:07 PM
Thank you for your feedback. At this time this request does not meet our bug bar.
Sign in to post a workaround.