Bug #13178 Shortcuts that should be Implemented

Submitted: 14 Sep 2005 12:05 Modified: 19 Sep 2005 19:21
Reporter: Mike Willbanks Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Workbench Preview Severity:S3 (Non-critical)
Version:Workbench 1.0.1a OS:Windows (Windows XP)
Assigned to: CPU Architecture:Any

[14 Sep 2005 12:05] Mike Willbanks
Description:
There are a bunch of shortcuts that could/should be made to make it easier for someone to model the diagram.  If also probable it would be ideal to make shortcuts editable by workbench "actions/commands".

Here are the items that should or could use shortcut keys:

Docked Windows:
(Not sure what keys..) Schema to Datatypes window
(Not sure what keys..) Layers to Properties window

Model Views:
Ctrl+Tab/Ctrl+Shift+Tab between Model Views
Ctrl+F4 or Ctrl+W to close Model Views

Operations:
Ctrl+Shift+S Save As

Alignment: (All go from left to right on the menu bar)
 - Vertical Alignment
Ctrl+A+1 Align Top Edges
Ctrl+A+2 Align Vertical Centers
Ctrl+A+3 Align Bottom Edges
 - Horizontal Alignment
Ctrl+A+4 Align Top Edges
Ctrl+A+5 Align Vertical Centers
Ctrl+A+6 Align Bottom Edges
 - Spaced Alignment
Ctrl+A+7 Align Vertical Centers
Ctrl+A+8 Align Vertical Centers

How to repeat:
Not Available.

Suggested fix:
Implement shortcuts.
[17 Sep 2005 5:27] Mike Willbanks
I figured that you guys don't really look at S4.  This one is shortcuts and is primarily usability based.
[22 Feb 2006 9:11] matthew heald
your alignment tools:
could you consider other aligment tools, such as align left.
reason: our dba / qa function are anal retentives and "demand" to see a data model in neat ordered columns & rows. I have already informed them that the chances of laying out links which do not overlap or dissappear behid tables is non existent.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.060 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.